From: Oscar Salvador <osalvador@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Hildenbrand <david@redhat.com>,
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,
Oscar Salvador <osalvador@suse.de>
Subject: [PATCH v5 5/5] arm64/Kconfig: Introduce ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE
Date: Fri, 19 Mar 2021 10:26:35 +0100 [thread overview]
Message-ID: <20210319092635.6214-6-osalvador@suse.de> (raw)
In-Reply-To: <20210319092635.6214-1-osalvador@suse.de>
Enable arm64 platform to use the MHP_MEMMAP_ON_MEMORY feature.
Signed-off-by: Oscar Salvador <osalvador@suse.de>
Reviewed-by: David Hildenbrand <david@redhat.com>
---
arch/arm64/Kconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 1f212b47a48a..c4ade8b47cf8 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -309,6 +309,9 @@ config ARCH_ENABLE_MEMORY_HOTPLUG
config ARCH_ENABLE_MEMORY_HOTREMOVE
def_bool y
+config ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE
+ def_bool y
+
config SMP
def_bool y
--
2.16.3
prev parent reply other threads:[~2021-03-19 9:26 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 9:26 [PATCH v5 0/5] Allocate memmap from hotadded memory (per device) Oscar Salvador
2021-03-19 9:26 ` [PATCH v5 1/5] mm,memory_hotplug: Allocate memmap from the added memory range Oscar Salvador
2021-03-19 10:20 ` David Hildenbrand
2021-03-19 10:31 ` Oscar Salvador
2021-03-19 12:04 ` David Hildenbrand
2021-03-23 10:11 ` Michal Hocko
2021-03-24 10:12 ` Oscar Salvador
2021-03-24 12:03 ` Michal Hocko
2021-03-24 12:10 ` Michal Hocko
2021-03-24 12:23 ` David Hildenbrand
2021-03-24 12:37 ` Michal Hocko
2021-03-24 13:13 ` David Hildenbrand
2021-03-24 13:40 ` Michal Hocko
2021-03-24 14:05 ` David Hildenbrand
2021-03-24 13:27 ` Oscar Salvador
2021-03-24 14:42 ` Michal Hocko
2021-03-24 14:52 ` David Hildenbrand
2021-03-24 16:04 ` Michal Hocko
2021-03-24 19:16 ` David Hildenbrand
2021-03-25 8:07 ` Oscar Salvador
2021-03-25 9:17 ` Michal Hocko
2021-03-25 10:55 ` Oscar Salvador
2021-03-25 11:08 ` David Hildenbrand
2021-03-25 11:23 ` Oscar Salvador
2021-03-25 12:35 ` Michal Hocko
2021-03-25 12:40 ` David Hildenbrand
2021-03-25 14:08 ` Michal Hocko
2021-03-25 14:09 ` David Hildenbrand
2021-03-25 14:34 ` Michal Hocko
2021-03-25 14:46 ` David Hildenbrand
2021-03-25 15:12 ` Michal Hocko
2021-03-25 15:19 ` David Hildenbrand
2021-03-25 15:35 ` Michal Hocko
2021-03-25 15:40 ` David Hildenbrand
2021-03-25 16:07 ` Michal Hocko
2021-03-25 16:20 ` David Hildenbrand
2021-03-25 16:36 ` Michal Hocko
2021-03-25 16:47 ` Michal Hocko
2021-03-25 16:55 ` David Hildenbrand
2021-03-25 22:06 ` Oscar Salvador
2021-03-26 8:35 ` Michal Hocko
2021-03-26 8:52 ` David Hildenbrand
2021-03-26 8:57 ` Oscar Salvador
2021-03-26 12:15 ` Oscar Salvador
2021-03-26 13:36 ` David Hildenbrand
2021-03-26 14:38 ` Michal Hocko
2021-03-26 14:53 ` David Hildenbrand
2021-03-26 15:31 ` Michal Hocko
2021-03-26 16:03 ` David Hildenbrand
2021-03-26 8:55 ` Oscar Salvador
2021-03-26 9:11 ` Michal Hocko
2021-03-25 18:08 ` David Hildenbrand
2021-03-25 12:26 ` Michal Hocko
2021-03-25 14:02 ` Oscar Salvador
2021-03-25 14:40 ` Michal Hocko
2021-03-19 9:26 ` [PATCH v5 2/5] acpi,memhotplug: Enable MHP_MEMMAP_ON_MEMORY when supported Oscar Salvador
2021-03-23 10:40 ` Michal Hocko
2021-03-19 9:26 ` [PATCH v5 3/5] mm,memory_hotplug: Add kernel boot option to enable memmap_on_memory Oscar Salvador
2021-03-23 10:47 ` Michal Hocko
2021-03-24 8:45 ` Oscar Salvador
2021-03-24 9:02 ` Michal Hocko
2021-03-19 9:26 ` [PATCH v5 4/5] x86/Kconfig: Introduce ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE Oscar Salvador
2021-03-19 9:26 ` Oscar Salvador [this message]
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=20210319092635.6214-6-osalvador@suse.de \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).