[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200416104707.20219-1-david@redhat.com>
Date: Thu, 16 Apr 2020 12:47:05 +0200
From: David Hildenbrand <david@...hat.com>
To: linux-kernel@...r.kernel.org
Cc: linux-mm@...ck.org, David Hildenbrand <david@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Anshuman Khandual <anshuman.khandual@....com>,
Baoquan He <bhe@...hat.com>, Michal Hocko <mhocko@...nel.org>,
Mike Rapoport <rppt@...ux.ibm.com>,
Oscar Salvador <osalvador@...e.de>,
Pankaj Gupta <pankaj.gupta.linux@...il.com>
Subject: [PATCH RFC 0/2] mm/memory_hotplug: handle memblocks only with CONFIG_ARCH_KEEP_MEMBLOCK
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
Powered by blists - more mailing lists