Messages in this thread | | | From | David Hildenbrand <> | Subject | [PATCH v1 0/2] mm/memory_hotplug: handle memblocks only with CONFIG_ARCH_KEEP_MEMBLOCK | Date | Wed, 22 Apr 2020 17:53:51 +0200 |
| |
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.
Gave it a quick test on x86-64.
RFC -> v1: - Added ACKs - Rephrased subject/description of patch #1 - Use IS_ENABLED() instead of ifdefs in patch #2
David Hildenbrand (2): mm/memory_hotplug: set node_start_pfn of hotadded pgdat to 0 mm/memory_hotplug: handle memblocks only with CONFIG_ARCH_KEEP_MEMBLOCK
mm/Kconfig | 3 +++ mm/memory_hotplug.c | 35 ++++++++++++++++------------------- 2 files changed, 19 insertions(+), 19 deletions(-)
-- 2.25.3
| |