[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dc044ae2-efce-0639-87de-3a3167c07a06@redhat.com>
Date: Thu, 25 Feb 2021 19:29:07 +0100
From: David Hildenbrand <david@...hat.com>
To: Oscar Salvador <osalvador@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: Michal Hocko <mhocko@...nel.org>, VlastimilBabkavbabka@...e.cz,
pasha.tatashin@...een.com, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Anshuman Khandual <anshuman.khandual@....com>
Subject: Re: [PATCH v2 6/7] x86/Kconfig: Introduce
ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE
On 09.02.21 14:38, Oscar Salvador wrote:
> Enable x86_64 platform to use the MHP_MEMMAP_ON_MEMORY feature.
>
> Signed-off-by: Oscar Salvador <osalvador@...e.de>
> ---
> arch/x86/Kconfig | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 72663de8b04c..81046b7adb10 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -2440,6 +2440,10 @@ config ARCH_ENABLE_MEMORY_HOTREMOVE
> def_bool y
> depends on MEMORY_HOTPLUG
>
> +config ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE
> + def_bool y
> + depends on X86_64 && MEMORY_HOTPLUG && SPARSEMEM_VMEMMAP_ENABLE
It depends on SPARSEMEM_VMEMMAP, no?
I think we could have
SPARSEMEM_VMEMMAP_ENABLE=y
and
SPARSEMEM_VMEMMAP=n
on manually tuned configs.
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists