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 v3 0/5] pseries NUMA distance calculation
Date: Tue, 29 Sep 2020 10:38:12 -0300 [thread overview]
Message-ID: <20200929133817.560278-1-danielhb413@gmail.com> (raw)
This third version is based on review comments and suggestion
from David.
changes from v2:
- patch 3 from v2: removed
- patch 2:
* added David's R-b
- patch 3 (former 4 in v2):
* added Greg and David R-bs
* added G_STATIC_ASSERT() before memcpy()
- patch 4 (former 5 in v2):
* clarified what 'node 0' means in the commit msg
* rewrote a bit to clarify what the logic does
* the translation of user distance to PAPR distance logic,
previously presented in the former patch 3 in v2, was folded
into spapr_numa_get_numa_level()
* removed needless 'if' when assigning associativities in
spapr_numa_define_associativity_domains()
- patch 5 (former 6 in v2):
* moved the section describing the current logic up
* created a new 'legacy' section describing the pre-5.2
behavior
* added a 'known limitations' section documentating that
we don't support asymmetrical topologies and we do a poor
job approximating 'non-transitive' topologies
v2 link: https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg09073.html
Daniel Henrique Barboza (5):
spapr: add spapr_machine_using_legacy_numa() helper
spapr_numa: forbid asymmetrical NUMA setups
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 | 206 +++++++++++++++++++++++++++++++++-
hw/ppc/spapr.c | 12 ++
hw/ppc/spapr_numa.c | 195 ++++++++++++++++++++++++++++++--
include/hw/ppc/spapr.h | 2 +
4 files changed, 406 insertions(+), 9 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-29 13:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 13:38 Daniel Henrique Barboza [this message]
2020-09-29 13:38 ` [PATCH v3 1/5] spapr: add spapr_machine_using_legacy_numa() helper Daniel Henrique Barboza
2020-09-29 13:38 ` [PATCH v3 2/5] spapr_numa: forbid asymmetrical NUMA setups Daniel Henrique Barboza
2020-09-29 13:38 ` [PATCH v3 3/5] spapr_numa: change reference-points and maxdomain settings Daniel Henrique Barboza
2020-09-29 13:38 ` [PATCH v3 4/5] spapr_numa: consider user input when defining associativity Daniel Henrique Barboza
2020-10-02 2:24 ` David Gibson
2020-10-02 13:02 ` Daniel Henrique Barboza
2020-09-29 13:38 ` [PATCH v3 5/5] specs/ppc-spapr-numa: update with new NUMA support Daniel Henrique Barboza
2020-10-02 3:16 ` 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=20200929133817.560278-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 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).