From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: qemu-devel@nongnu.org
Cc: Daniel Henrique Barboza <danielhb413@gmail.com>,
qemu-ppc@nongnu.org, groug@kaod.org, david@gibson.dropbear.id.au
Subject: [PATCH v2 0/6] pseries NUMA distance calculation
Date: Thu, 24 Sep 2020 16:50:52 -0300 [thread overview]
Message-ID: <20200924195058.362984-1-danielhb413@gmail.com> (raw)
This second version contains fixes based on the v1 review made
by Greg.
changes from v1:
- patch 1:
* added Greg's R-b
- patch 2:
* fixed 'order' typo
* changed exit(1) to exit(EXIT_FAILURE)
* added Greg's R-b
- patch 3:
* clarified in the function comment the rounding of distance
values 30, 60 and 120
* fixed a bug where distances 30, 60 and 120 wasn't being
PAPRified (use <= instead of just <)
- patch 4:
* made the changes multi-line and more explicit, allowing
to easily see the differences between current and legacy arrays
- patch 5:
* turned spapr_numa_get_NUMA_level() to lowercase
* added a switch clause for distance = 10
* removed MachineState parameter of
spapr_numa_define_associativity_domains()
* clarified the reason why the associativity domains need
to be initialized with 'node_id' in the comment
* we're now handling distances > 120 appropriately (no
NUMA match case)
v1 link: https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg08549.html
Daniel Henrique Barboza (6):
spapr: add spapr_machine_using_legacy_numa() helper
spapr_numa: forbid asymmetrical NUMA setups
spapr_numa: translate regular NUMA distance to PAPR distance
spapr_numa: change reference-points and maxdomain settings
spapr_numa: consider user input when defining associativity
specs/ppc-spapr-numa: update with new NUMA support
docs/specs/ppc-spapr-numa.rst | 213 +++++++++++++++++++++++++++++++++
hw/ppc/spapr.c | 12 ++
hw/ppc/spapr_numa.c | 217 ++++++++++++++++++++++++++++++++--
include/hw/ppc/spapr.h | 2 +
4 files changed, 436 insertions(+), 8 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-24 19:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 19:50 Daniel Henrique Barboza [this message]
2020-09-24 19:50 ` [PATCH v2 1/6] spapr: add spapr_machine_using_legacy_numa() helper Daniel Henrique Barboza
2020-09-24 19:50 ` [PATCH v2 2/6] spapr_numa: forbid asymmetrical NUMA setups Daniel Henrique Barboza
2020-09-25 2:36 ` David Gibson
2020-09-25 3:48 ` David Gibson
2020-09-25 12:41 ` Daniel Henrique Barboza
2020-09-26 7:49 ` David Gibson
2020-09-27 11:41 ` Daniel Henrique Barboza
2020-09-28 6:25 ` David Gibson
2020-09-24 19:50 ` [PATCH v2 3/6] spapr_numa: translate regular NUMA distance to PAPR distance Daniel Henrique Barboza
2020-09-25 2:35 ` David Gibson
2020-09-25 12:44 ` Daniel Henrique Barboza
2020-09-24 19:50 ` [PATCH v2 4/6] spapr_numa: change reference-points and maxdomain settings Daniel Henrique Barboza
2020-09-25 2:38 ` David Gibson
2020-09-25 13:16 ` Greg Kurz
2020-09-24 19:50 ` [PATCH v2 5/6] spapr_numa: consider user input when defining associativity Daniel Henrique Barboza
2020-09-25 3:39 ` David Gibson
2020-09-25 14:42 ` Daniel Henrique Barboza
2020-09-24 19:50 ` [PATCH v2 6/6] specs/ppc-spapr-numa: update with new NUMA support Daniel Henrique Barboza
2020-09-25 3:43 ` 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=20200924195058.362984-1-danielhb413@gmail.com \
--to=danielhb413@gmail.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.