From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Kaitao Cheng <kaitao.cheng@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R . Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Muchun Song <muchun.song@linux.dev>,
Kaitao Cheng <chengkaitao@kylinos.cn>
Subject: Re: [PATCH] mm/kconfig: Drop redundant memory hotplug dependencies
Date: Tue, 7 Jul 2026 12:06:07 +0200 [thread overview]
Message-ID: <776663aa-3378-4c55-8c2e-3231443dfee4@kernel.org> (raw)
In-Reply-To: <20260707090331.52971-1-kaitao.cheng@linux.dev>
On 7/7/26 11:03, Kaitao Cheng wrote:
> From: Kaitao Cheng <chengkaitao@kylinos.cn>
>
> MHP_MEMMAP_ON_MEMORY is defined inside the MEMORY_HOTPLUG block, and
> MEMORY_HOTPLUG already depends on SPARSEMEM_VMEMMAP. Keep the explicit
> MEMORY_HOTPLUG dependency for local readability, but drop the redundant
> SPARSEMEM_VMEMMAP dependency.
>
> ZONE_DEVICE depends on MEMORY_HOTREMOVE, which depends on MEMORY_HOTPLUG.
> MEMORY_HOTPLUG in turn depends on SPARSEMEM_VMEMMAP. Drop the direct
> MEMORY_HOTPLUG and SPARSEMEM_VMEMMAP dependencies from ZONE_DEVICE.
>
> This does not change the set of valid configurations.
>
> Signed-off-by: Kaitao Cheng <chengkaitao@kylinos.cn>
> ---
> mm/Kconfig | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/mm/Kconfig b/mm/Kconfig
> index 04fe5171bb8c..ff29f770d10a 100644
> --- a/mm/Kconfig
> +++ b/mm/Kconfig
> @@ -596,7 +596,7 @@ config MEMORY_HOTREMOVE
>
> config MHP_MEMMAP_ON_MEMORY
> def_bool y
> - depends on MEMORY_HOTPLUG && SPARSEMEM_VMEMMAP
> + depends on MEMORY_HOTPLUG
> depends on ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE
>
> endif # MEMORY_HOTPLUG
> @@ -1235,9 +1235,7 @@ config ZONE_DMA32
>
> config ZONE_DEVICE
> bool "Device memory (pmem, HMM, etc...) hotplug support"
> - depends on MEMORY_HOTPLUG
> depends on MEMORY_HOTREMOVE
> - depends on SPARSEMEM_VMEMMAP
> select XARRAY_MULTI
I'm planning on merging MEMORY_HOTPLUG and MEMORY_HOTREMOVE soon, but for now
that is good enough.
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
--
Cheers,
David
next prev parent reply other threads:[~2026-07-07 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 9:03 [PATCH] mm/kconfig: Drop redundant memory hotplug dependencies Kaitao Cheng
2026-07-07 10:06 ` David Hildenbrand (Arm) [this message]
2026-07-07 11:05 ` Muchun Song
2026-07-07 11:11 ` Lorenzo Stoakes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=776663aa-3378-4c55-8c2e-3231443dfee4@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chengkaitao@kylinos.cn \
--cc=kaitao.cheng@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox