From: Nicholas Piggin <npiggin@gmail.com>
To: qemu-ppc@nongnu.org
Cc: "Nicholas Piggin" <npiggin@gmail.com>,
qemu-devel@nongnu.org, "Eduardo Habkost" <eduardo@habkost.net>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Yanan Wang" <wangyanan55@huawei.com>,
"Zhao Liu" <zhao1.liu@intel.com>,
"Frédéric Barrat" <fbarrat@linux.ibm.com>,
"Igor Mammedov" <imammedo@redhat.com>
Subject: [PATCH 0/3] ppc/pnv: Support sparse NUMA memory addresses
Date: Mon, 3 Mar 2025 20:07:29 +1000 [thread overview]
Message-ID: <20250303100732.576457-1-npiggin@gmail.com> (raw)
IBM Power machines put NUMA node RAM at fixed addresses per node,
rather than packing it densely from address 0. This series implements
support for this by allowing machines to override the core NUMA
memory container packing, and add their own RAM regions to the
system memory space.
Thanks,
Nick
Nicholas Piggin (3):
ppc/pnv: Add support for NUMA configuration
hw/core/numa: add attribute to skip creation of MachineState.ram
region
ppc/pnv: Enable sparse chip RAM memory addresses
include/hw/boards.h | 6 ++
include/system/numa.h | 1 +
hw/core/numa.c | 44 +++++++++++---
hw/ppc/pnv.c | 138 +++++++++++++++++++++++++++++++++++++-----
4 files changed, 166 insertions(+), 23 deletions(-)
--
2.47.1
next reply other threads:[~2025-03-03 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 10:07 Nicholas Piggin [this message]
2025-03-03 10:07 ` [PATCH 1/3] ppc/pnv: Add support for NUMA configuration Nicholas Piggin
2025-03-03 10:07 ` [PATCH 2/3] hw/core/numa: add attribute to skip creation of MachineState.ram region Nicholas Piggin
2025-03-03 10:07 ` [PATCH 3/3] ppc/pnv: Enable sparse chip RAM memory addresses Nicholas Piggin
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=20250303100732.576457-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=eduardo@habkost.net \
--cc=fbarrat@linux.ibm.com \
--cc=imammedo@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=wangyanan55@huawei.com \
--cc=zhao1.liu@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;
as well as URLs for NNTP newsgroup(s).