summaryrefslogtreecommitdiff
path: root/arch/arm/vdso
diff options
context:
space:
mode:
authorMike Rapoport <rppt@linux.ibm.com>2021-12-13 12:41:31 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2021-12-17 12:14:42 +0300
commitb4b54c7ba149ffa2dcb11b2a84ebf20189ff7f89 (patch)
tree59f9922f2913e5227faf248467d040e17006cd4d /arch/arm/vdso
parentb6a1cbd187fc7addddcb9c669f7362dec4d54595 (diff)
downloadlinux-b4b54c7ba149ffa2dcb11b2a84ebf20189ff7f89.tar.xz
memblock: free_unused_memmap: use pageblock units instead of MAX_ORDER
[ Upstream commit e2a86800d58639b3acde7eaeb9eb393dca066e08 ] The code that frees unused memory map uses rounds start and end of the holes that are freed to MAX_ORDER_NR_PAGES to preserve continuity of the memory map for MAX_ORDER regions. Lots of core memory management functionality relies on homogeneity of the memory map within each pageblock which size may differ from MAX_ORDER in certain configurations. Although currently, for the architectures that use free_unused_memmap(), pageblock_order and MAX_ORDER are equivalent, it is cleaner to have common notation thought mm code. Replace MAX_ORDER_NR_PAGES with pageblock_nr_pages and update the comments to make it more clear why the alignment to pageblock boundaries is required. Signed-off-by: Mike Rapoport <rppt@linux.ibm.com> Tested-by: Tony Lindgren <tony@atomide.com> Link: https://lore.kernel.org/lkml/20210630071211.21011-1-rppt@kernel.org/ [backport upstream modification in mm/memblock.c to arch/arm/mm/init.c] Signed-off-by: Mark-PK Tsai <mark-pk.tsai@mediatek.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/arm/vdso')
0 files changed, 0 insertions, 0 deletions