Messages in this thread Patch in this message |  | | From | Wei Yang <> | Subject | [PATCH 1/2] mm/page_vma_mapped: use PMD_SIZE instead of calculating it | Date | Thu, 28 Nov 2019 09:03:20 +0800 |
| |
At this point, we are sure page is PageTransHuge, which means hpage_nr_pages is HPAGE_PMD_NR.
This is safe to use PMD_SIZE instead of calculating it.
Signed-off-by: Wei Yang <richardw.yang@linux.intel.com> --- mm/page_vma_mapped.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/page_vma_mapped.c b/mm/page_vma_mapped.c index eff4b4520c8d..76e03650a3ab 100644 --- a/mm/page_vma_mapped.c +++ b/mm/page_vma_mapped.c @@ -223,7 +223,7 @@ bool page_vma_mapped_walk(struct page_vma_mapped_walk *pvmw) if (pvmw->address >= pvmw->vma->vm_end || pvmw->address >= __vma_address(pvmw->page, pvmw->vma) + - hpage_nr_pages(pvmw->page) * PAGE_SIZE) + PMD_SIZE) return not_found(pvmw); /* Did we cross page table boundary? */ if (pvmw->address % PMD_SIZE == 0) { -- 2.17.1
|  |