While working on some other cleanups I stumbled over the creation/removal
of memblocks in hotplug code and wondered why we still need that. Turns
out, we only need that handling with CONFIG_ARCH_KEEP_MEMBLOCK - unless
I am missing something important (-> RFC).
I'll be sending out patches to remove CONFIG_ARCH_KEEP_MEMBLOCK on s390x
soonish, after finding a way to test them.
Gave it a quick test on x86-64.
David Hildenbrand (2):
mm/memory_hotplug: no need to init new pgdat with node_start_pfn
mm/memory_hotplug: handle memblocks only with
CONFIG_ARCH_KEEP_MEMBLOCK
mm/Kconfig | 3 +++
mm/memory_hotplug.c | 28 +++++++++++++---------------
2 files changed, 16 insertions(+), 15 deletions(-)
--
2.25.1
