From: David Gibson <david@gibson.dropbear.id.au>
To: Daniel Henrique Barboza <danielhb413@gmail.com>
Cc: aneesh.kumar@linux.ibm.com, qemu-ppc@nongnu.org,
qemu-devel@nongnu.org, groug@kaod.org
Subject: Re: [RFC PATCH v2 0/7] pSeries base FORM2 NUMA affinity support
Date: Thu, 24 Jun 2021 15:47:05 +1000 [thread overview]
Message-ID: <YNQcWSsQj0PFhb08@yekko> (raw)
In-Reply-To: <20210616011944.2996399-1-danielhb413@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]
On Tue, Jun 15, 2021 at 10:19:37PM -0300, Daniel Henrique Barboza wrote:
> Hi,
>
> This new version contains changes made after reviews from Aneesh
> and David in v1.
I might hold off on reviewing the qemu patches until the kernel
patches (and the exact design of the dt stuff) are more settled.
>
> 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 (7):
> 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
> nvdimm: add PPC64 'device-node' property
> spapr_numa, spapr_nvdimm: write secondary NUMA domain for nvdimms
> spapr: move memory/cpu less check to spapr_numa_FORM1_affinity_init()
>
> hw/mem/nvdimm.c | 31 +++++
> hw/ppc/spapr.c | 60 ++++-----
> hw/ppc/spapr_hcall.c | 4 +
> hw/ppc/spapr_numa.c | 257 +++++++++++++++++++++++++++++++++---
> hw/ppc/spapr_nvdimm.c | 5 +-
> include/hw/mem/nvdimm.h | 12 ++
> include/hw/ppc/spapr.h | 1 +
> include/hw/ppc/spapr_numa.h | 6 +-
> include/hw/ppc/spapr_ovec.h | 1 +
> 9 files changed, 318 insertions(+), 59 deletions(-)
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-06-24 6:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 1:19 [RFC PATCH v2 0/7] pSeries base FORM2 NUMA affinity support Daniel Henrique Barboza
2021-06-16 1:19 ` [RFC PATCH v2 1/7] spapr_numa.c: split FORM1 code into helpers Daniel Henrique Barboza
2021-06-16 1:19 ` [RFC PATCH v2 2/7] spapr: move NUMA data init to post-CAS Daniel Henrique Barboza
2021-06-16 1:19 ` [RFC PATCH v2 3/7] spapr_numa.c: base FORM2 NUMA affinity support Daniel Henrique Barboza
2021-06-16 1:19 ` [RFC PATCH v2 4/7] spapr: simplify spapr_numa_associativity_init params Daniel Henrique Barboza
2021-06-16 1:19 ` [RFC PATCH v2 5/7] nvdimm: add PPC64 'device-node' property Daniel Henrique Barboza
2021-06-16 1:19 ` [RFC PATCH v2 6/7] spapr_numa, spapr_nvdimm: write secondary NUMA domain for nvdimms Daniel Henrique Barboza
2021-06-16 1:19 ` [RFC PATCH v2 7/7] spapr: move memory/cpu less check to spapr_numa_FORM1_affinity_init() Daniel Henrique Barboza
2021-06-24 5:47 ` David Gibson [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=YNQcWSsQj0PFhb08@yekko \
--to=david@gibson.dropbear.id.au \
--cc=aneesh.kumar@linux.ibm.com \
--cc=danielhb413@gmail.com \
--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 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).