summaryrefslogtreecommitdiffstats
path: root/arch/x86/mm/init_64.c
diff options
context:
space:
mode:
authorMichal Hocko <mhocko@suse.com>2019-05-14 02:21:24 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2019-05-14 18:47:49 +0200
commit5557c766abad25acc8091ccb9641b96e3b3da06f (patch)
tree37c82ae65becf5198a2b4a213558b1e9d645a67f /arch/x86/mm/init_64.c
parentmm: initialize MAX_ORDER_NR_PAGES at a time instead of doing larger sections (diff)
downloadlinux-5557c766abad25acc8091ccb9641b96e3b3da06f.tar.xz
linux-5557c766abad25acc8091ccb9641b96e3b3da06f.zip
mm, memory_hotplug: cleanup memory offline path
check_pages_isolated_cb currently accounts the whole pfn range as being offlined if test_pages_isolated suceeds on the range. This is based on the assumption that all pages in the range are freed which is currently the case in most cases but it won't be with later changes, as pages marked as vmemmap won't be isolated. Move the offlined pages counting to offline_isolated_pages_cb and rely on __offline_isolated_pages to return the correct value. check_pages_isolated_cb will still do it's primary job and check the pfn range. While we are at it remove check_pages_isolated and offline_isolated_pages and use directly walk_system_ram_range as do in online_pages. Link: http://lkml.kernel.org/r/20190408082633.2864-2-osalvador@suse.de Reviewed-by: David Hildenbrand <david@redhat.com> Signed-off-by: Michal Hocko <mhocko@suse.com> Signed-off-by: Oscar Salvador <osalvador@suse.de> Cc: Dan Williams <dan.j.williams@intel.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/x86/mm/init_64.c')
0 files changed, 0 insertions, 0 deletions