From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: qemu-devel@nongnu.org
Cc: aneesh.kumar@linux.ibm.com,
Daniel Henrique Barboza <danielhb413@gmail.com>,
qemu-ppc@nongnu.org, groug@kaod.org, david@gibson.dropbear.id.au
Subject: [RFC PATCH v3 0/5] pSeries FORM2 affinity support
Date: Tue, 13 Jul 2021 16:40:40 -0300 [thread overview]
Message-ID: <20210713194045.916263-1-danielhb413@gmail.com> (raw)
Hi,
This new version drops all the NVDIMM related changes from the
previous iteraction after the reviews done in the kernel mailing
list [1]. FORM2 will not use ibm,associativity-reference-points to
determine a second NUMA mode for different operation modes of
PAPR-SCM.
[1] https://lore.kernel.org/linuxppc-dev/20210628151117.545935-1-aneesh.kumar@linux.ibm.com/
changes from v2:
- patch 3:
* reworded commit msg and comments to reflect the current state of
the specification
- patches 5 and 6: removed
- v2 link: https://lists.gnu.org/archive/html/qemu-devel/2021-06/msg04056.html
changes from v1:
- patches 1 and 2: switched places
- patch 3: folded into patch 2
- patch 2:
* only make CAS related changes when using the newest
machine version
- patch 3 (former 4):
* only advertise FORM2 support for the newest machine version
- patches 5 and 6 (former 6 and 7):
* detect if 'device-node' was set in the command line, and if not,
use the 'node' value when writing in the device tree
v1 link: https://lists.gnu.org/archive/html/qemu-devel/2021-06/msg03617.html
Daniel Henrique Barboza (5):
spapr_numa.c: split FORM1 code into helpers
spapr: move NUMA data init to post-CAS
spapr_numa.c: base FORM2 NUMA affinity support
spapr: simplify spapr_numa_associativity_init params
spapr: move memory/cpu less check to spapr_numa_FORM1_affinity_init()
hw/ppc/spapr.c | 60 ++++------
hw/ppc/spapr_hcall.c | 4 +
hw/ppc/spapr_numa.c | 224 +++++++++++++++++++++++++++++++++---
include/hw/ppc/spapr.h | 1 +
include/hw/ppc/spapr_numa.h | 3 +-
include/hw/ppc/spapr_ovec.h | 1 +
6 files changed, 236 insertions(+), 57 deletions(-)
--
2.31.1
next reply other threads:[~2021-07-13 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 19:40 Daniel Henrique Barboza [this message]
2021-07-13 19:40 ` [RFC PATCH v3 1/5] spapr_numa.c: split FORM1 code into helpers Daniel Henrique Barboza
2021-07-13 19:40 ` [RFC PATCH v3 2/5] spapr: move NUMA data init to post-CAS Daniel Henrique Barboza
2021-07-13 19:40 ` [RFC PATCH v3 3/5] spapr_numa.c: base FORM2 NUMA affinity support Daniel Henrique Barboza
2021-07-13 19:40 ` [RFC PATCH v3 4/5] spapr: simplify spapr_numa_associativity_init params Daniel Henrique Barboza
2021-07-13 19:40 ` [RFC PATCH v3 5/5] spapr: move memory/cpu less check to spapr_numa_FORM1_affinity_init() Daniel Henrique Barboza
2021-07-22 2:39 ` [RFC PATCH v3 0/5] pSeries FORM2 affinity support David Gibson
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=20210713194045.916263-1-danielhb413@gmail.com \
--to=danielhb413@gmail.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.