From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: linux-mm@kvack.org, akpm@linux-foundation.org,
mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org,
npiggin@gmail.com, christophe.leroy@csgroup.eu
Cc: Oscar Salvador <osalvador@suse.de>,
David Hildenbrand <david@redhat.com>,
Michal Hocko <mhocko@suse.com>,
Vishal Verma <vishal.l.verma@intel.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Subject: [PATCH v2 0/5] Add support for memmap on memory feature on ppc64
Date: Thu, 6 Jul 2023 14:20:36 +0530 [thread overview]
Message-ID: <20230706085041.826340-1-aneesh.kumar@linux.ibm.com> (raw)
This patch series update memmap on memory feature to fall back to
memmap allocation outside the memory block if the alignment rules are
not met. This makes the feature more useful on architectures like
ppc64 where alignment rules are different with 64K page size.
This patch series is dependent on dax vmemmap optimization series
posted here https://lore.kernel.org/linux-mm/20230616110826.344417-1-aneesh.kumar@linux.ibm.com
Changes from v1:
* update the memblock to store vmemmap_altmap details. This is required
so that when we remove the memory we can find the altmap details which
is needed on some architectures.
* rebase to latest linus tree
Aneesh Kumar K.V (5):
mm/hotplug: Embed vmem_altmap details in memory block
mm/hotplug: Allow architecture override for memmap on memory feature
mm/hotplug: Simplify the handling of MHP_MEMMAP_ON_MEMORY flag
mm/hotplug: Simplify ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE kconfig
powerpc/book3s64/memhotplug: Enable memmap on memory for radix
arch/arm64/Kconfig | 4 +-
arch/arm64/mm/mmu.c | 5 +
arch/powerpc/Kconfig | 1 +
arch/powerpc/mm/book3s64/radix_pgtable.c | 28 ++++++
.../platforms/pseries/hotplug-memory.c | 4 +-
arch/x86/Kconfig | 4 +-
arch/x86/mm/init_64.c | 6 ++
drivers/acpi/acpi_memhotplug.c | 3 +-
drivers/base/memory.c | 28 ++++--
include/linux/memory.h | 25 +++--
include/linux/memory_hotplug.h | 17 +++-
include/linux/memremap.h | 18 +---
mm/Kconfig | 3 +
mm/memory_hotplug.c | 94 +++++++++----------
14 files changed, 151 insertions(+), 89 deletions(-)
--
2.41.0
next reply other threads:[~2023-07-06 8:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 8:50 Aneesh Kumar K.V [this message]
2023-07-06 8:50 ` [PATCH v2 1/5] mm/hotplug: Embed vmem_altmap details in memory block Aneesh Kumar K.V
2023-07-06 9:18 ` David Hildenbrand
2023-07-06 9:36 ` Aneesh Kumar K V
2023-07-06 11:14 ` David Hildenbrand
2023-07-06 12:32 ` Aneesh Kumar K V
2023-07-06 12:59 ` David Hildenbrand
2023-07-06 16:06 ` Aneesh Kumar K V
2023-07-07 12:17 ` David Hildenbrand
2023-07-07 13:30 ` Aneesh Kumar K V
2023-07-07 15:42 ` David Hildenbrand
2023-07-07 16:25 ` Aneesh Kumar K V
2023-07-07 20:26 ` David Hildenbrand
2023-07-06 8:50 ` [PATCH v2 2/5] mm/hotplug: Allow architecture override for memmap on memory feature Aneesh Kumar K.V
2023-07-06 9:19 ` David Hildenbrand
2023-07-06 8:50 ` [PATCH v2 3/5] mm/hotplug: Simplify the handling of MHP_MEMMAP_ON_MEMORY flag Aneesh Kumar K.V
2023-07-06 9:24 ` David Hildenbrand
2023-07-06 10:04 ` Aneesh Kumar K V
2023-07-06 11:20 ` David Hildenbrand
2023-07-06 8:50 ` [PATCH v2 4/5] mm/hotplug: Simplify ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE kconfig Aneesh Kumar K.V
2023-07-06 8:53 ` David Hildenbrand
2023-07-06 8:50 ` [PATCH v2 5/5] powerpc/book3s64/memhotplug: Enable memmap on memory for radix Aneesh Kumar K.V
2023-07-06 9:07 ` David Hildenbrand
2023-07-06 9:27 ` Aneesh Kumar K V
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=20230706085041.826340-1-aneesh.kumar@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=christophe.leroy@csgroup.eu \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@suse.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=osalvador@suse.de \
--cc=vishal.l.verma@intel.com \
/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