From: David Hildenbrand <david@redhat.com>
To: Oscar Salvador <osalvador@suse.de>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Vlastimil Babka <vbabka@suse.cz>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/5] x86/Kconfig: Introduce ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE
Date: Fri, 5 Mar 2021 16:32:07 +0100 [thread overview]
Message-ID: <a1df6c58-dab6-3eea-fbd9-3b25c887fc73@redhat.com> (raw)
In-Reply-To: <20210304100002.7740-5-osalvador@suse.de>
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@suse.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@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-03-05 15:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 9:59 [PATCH v3 0/5] Allocate memmap from hotadded memory (per device) Oscar Salvador
2021-03-04 9:59 ` [PATCH v3 1/5] mm,memory_hotplug: Allocate memmap from the added memory range Oscar Salvador
2021-03-08 3:16 ` Zi Yan
2021-03-08 14:04 ` Oscar Salvador
2021-03-08 14:06 ` David Hildenbrand
2021-03-04 9:59 ` [PATCH v3 2/5] acpi,memhotplug: Enable MHP_MEMMAP_ON_MEMORY when supported Oscar Salvador
2021-03-04 10:00 ` [PATCH v3 3/5] mm,memory_hotplug: Add kernel boot option to enable memmap_on_memory Oscar Salvador
2021-03-05 15:35 ` David Hildenbrand
2021-03-08 15:46 ` Oscar Salvador
2021-03-04 10:00 ` [PATCH v3 4/5] x86/Kconfig: Introduce ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE Oscar Salvador
2021-03-05 15:32 ` David Hildenbrand [this message]
2021-03-07 22:14 ` Oscar Salvador
2021-03-04 10:00 ` [PATCH v3 5/5] arm64/Kconfig: " Oscar Salvador
2021-03-05 15:32 ` David Hildenbrand
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=a1df6c58-dab6-3eea-fbd9-3b25c887fc73@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.com \
--cc=vbabka@suse.cz \
/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