mm/mremap: calculate extent in one place
Page tables is moved on the base of PMD. This requires both source and
destination range should meet the requirement.
Current code works well since move_huge_pmd() and move_normal_pmd() would
check old_addr and new_addr again. And then return to move_ptes() if the
either of them is not aligned.
Instead of calculating the extent separately, it is better to calculate in
one place, so we know it is not necessary to try move pmd. By doing so,
the logic seems a little clear.
Signed-off-by: Wei Yang <firstname.lastname@example.org>
Signed-off-by: Andrew Morton <email@example.com>
Tested-by: Dmitry Osipenko <firstname.lastname@example.org>
Acked-by: Kirill A. Shutemov <email@example.com>
Cc: Aneesh Kumar K.V <firstname.lastname@example.org>
Cc: Anshuman Khandual <email@example.com>
Cc: Matthew Wilcox <firstname.lastname@example.org>
Cc: Peter Xu <email@example.com>
Cc: Sean Christopherson <firstname.lastname@example.org>
Cc: Thomas Hellstrom <email@example.com>
Cc: Thomas Hellstrom (VMware) <firstname.lastname@example.org>
Cc: Vlastimil Babka <email@example.com>
Cc: Yang Shi <firstname.lastname@example.org>
Signed-off-by: Linus Torvalds <email@example.com>
1 file changed