From: David Gibson <david@gibson.dropbear.id.au>
To: Daniel Henrique Barboza <danielhb413@gmail.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v3 0/7] pseries NUMA distance rework
Date: Fri, 4 Sep 2020 09:23:00 +1000 [thread overview]
Message-ID: <20200903232300.GA341806@yekko.fritz.box> (raw)
In-Reply-To: <20200903220639.563090-1-danielhb413@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2479 bytes --]
On Thu, Sep 03, 2020 at 07:06:32PM -0300, Daniel Henrique Barboza wrote:
> Hi,
>
> This spin attempts to cover all suggestions and concerns pointed
> out by David Gibson in the v2 review.
>
> The patches were rebased with David's ppc-for-5.2 at 615ae3763144.
> They can also be cloned from
> https://github.com/danielhb/qemu/tree/spapr_numa_v3.
>
> Changes from v2:
> - patches 1 and 2 from v2 -> already pushed to ppc-for-5.2
> - patch 1 (former 3):
> * numa_assoc_array moved to SpaprMachineState
> - patch 3 (former 5):
> * use memcpy
> * fix index increment to use MAX_DISTANCE_REF_POINTS
> - patch 4 (former 6):
> * revamped. NVLink2 associativity is now calculated in
> spapr_numa_associativity_init(). GPU code will use the same
> helper everyone but vcpus uses to write the associativity DT
> - patch 5 - new
> - patch 6 - new
> - patch 7:
> * no more brazilian portuguese notes in the commit message
> * change the code to handle an arbitrary vcpu associativity
> array, retrieved with a new helper added by patch 6.
>
> v2 link:
> https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg00261.html
I've applied 1..4, though I will comment on some nits that could be
cleaned up later on. I have some bigger comments on the remainder.
>
>
> Daniel Henrique Barboza (7):
> spapr: introduce SpaprMachineState::numa_assoc_array
> spapr, spapr_numa: handle vcpu ibm,associativity
> spapr, spapr_numa: move lookup-arrays handling to spapr_numa.c
> spapr_numa: move NVLink2 associativity handling to spapr_numa.c
> spapr: move h_home_node_associativity to spapr_numa.c
> spapr_numa: create a vcpu associativity helper
> spapr_numa: use spapr_numa_get_vcpu_assoc() in home_node hcall
>
> hw/ppc/spapr.c | 65 +++---------
> hw/ppc/spapr_hcall.c | 37 +------
> hw/ppc/spapr_numa.c | 184 ++++++++++++++++++++++++++++++++++
> hw/ppc/spapr_nvdimm.c | 19 ++--
> hw/ppc/spapr_pci.c | 9 +-
> hw/ppc/spapr_pci_nvlink2.c | 20 +---
> include/hw/ppc/spapr.h | 12 +++
> include/hw/ppc/spapr_numa.h | 19 ++++
> include/hw/ppc/spapr_nvdimm.h | 2 +-
> 9 files changed, 242 insertions(+), 125 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:[~2020-09-03 23:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 22:06 [PATCH v3 0/7] pseries NUMA distance rework Daniel Henrique Barboza
2020-09-03 22:06 ` [PATCH v3 1/7] spapr: introduce SpaprMachineState::numa_assoc_array Daniel Henrique Barboza
2020-09-03 22:06 ` [PATCH v3 2/7] spapr, spapr_numa: handle vcpu ibm,associativity Daniel Henrique Barboza
2020-09-03 23:23 ` David Gibson
2020-09-04 0:32 ` Daniel Henrique Barboza
2020-09-03 22:06 ` [PATCH v3 3/7] spapr, spapr_numa: move lookup-arrays handling to spapr_numa.c Daniel Henrique Barboza
2020-09-03 22:06 ` [PATCH v3 4/7] spapr_numa: move NVLink2 associativity " Daniel Henrique Barboza
2020-09-03 22:06 ` [PATCH v3 5/7] spapr: move h_home_node_associativity " Daniel Henrique Barboza
2020-09-03 23:25 ` David Gibson
2020-09-03 22:06 ` [PATCH v3 6/7] spapr_numa: create a vcpu associativity helper Daniel Henrique Barboza
2020-09-03 23:27 ` David Gibson
2020-09-03 22:06 ` [PATCH v3 7/7] spapr_numa: use spapr_numa_get_vcpu_assoc() in home_node hcall Daniel Henrique Barboza
2020-09-03 23:31 ` David Gibson
2020-09-03 23:23 ` 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=20200903232300.GA341806@yekko.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=danielhb413@gmail.com \
--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).