[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a1df6c58-dab6-3eea-fbd9-3b25c887fc73@redhat.com>
Date: Fri, 5 Mar 2021 16:32: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>,
Anshuman Khandual <anshuman.khandual@....com>,
Vlastimil Babka <vbabka@...e.cz>,
Pavel Tatashin <pasha.tatashin@...een.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 4/5] x86/Kconfig: Introduce
ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE
On 04.03.21 11:00, 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 2792879d398e..6d716d8bce1e 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -2433,6 +2433,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
Was wondering if the MEMORY_HOTPLUG would also best be part of the
generic MHP_MEMMAP_ON_MEMORY.
Apart from that
Reviewed-by: David Hildenbrand <david@...hat.com>
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists