From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: qemu-devel@nongnu.org
Cc: Daniel Henrique Barboza <danielhb413@gmail.com>,
qemu-ppc@nongnu.org, david@gibson.dropbear.id.au
Subject: [PATCH 0/6] pseries NUMA distance calculation
Date: Wed, 23 Sep 2020 16:34:52 -0300 [thread overview]
Message-ID: <20200923193458.203186-1-danielhb413@gmail.com> (raw)
Hi,
This series is a follow-up of the reworked pSeries NUMA
code that is already merged upstream. It contains some of
the patches that were presented in the first version of this
work [1], some of them changed based on the reviews made
back there.
With this series, we're able to take user input into consideration
when setting up the NUMA topology of the guest. It is still an
approximation, but at least user input is not completely ignored.
The changes will only be effective with pseries-5.2 and newer
machines, and if more than one NUMA node is declared by the user.
The idea is that we don't want to tamper with legacy guest behavior.
Patch 6 has examples of how we are approximating NUMA distance
via user input.
The series was rebased using David's ppc-for-5.2 at
4cca31df828.
Changes carried over from [1]:
- patch 1 (former 4): same patch, added David's r-b
- patch 2 (former 2): the check for asymetrical NUMA was moved
to spapr code as requested in the review
- patch 4 is a merge of former patches 5 and 6
- patch 5 (former 9): reworked
- patch 6 (former 10): same patch
Patch 3 is new in the series.
[1] https://lists.gnu.org/archive/html/qemu-devel/2020-08/msg03169.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 | 184 +++++++++++++++++++++++++++--
include/hw/ppc/spapr.h | 2 +
4 files changed, 402 insertions(+), 9 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-23 19:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 19:34 Daniel Henrique Barboza [this message]
2020-09-23 19:34 ` [PATCH 1/6] spapr: add spapr_machine_using_legacy_numa() helper Daniel Henrique Barboza
2020-09-24 7:47 ` Greg Kurz
2020-09-23 19:34 ` [PATCH 2/6] spapr_numa: forbid asymmetrical NUMA setups Daniel Henrique Barboza
2020-09-24 8:01 ` Greg Kurz
2020-09-24 11:23 ` Daniel Henrique Barboza
2020-09-23 19:34 ` [PATCH 3/6] spapr_numa: translate regular NUMA distance to PAPR distance Daniel Henrique Barboza
2020-09-24 8:16 ` Greg Kurz
2020-09-24 11:18 ` Daniel Henrique Barboza
2020-09-23 19:34 ` [PATCH 4/6] spapr_numa: change reference-points and maxdomain settings Daniel Henrique Barboza
2020-09-24 9:33 ` Greg Kurz
2020-09-23 19:34 ` [PATCH 5/6] spapr_numa: consider user input when defining associativity Daniel Henrique Barboza
2020-09-24 10:22 ` Greg Kurz
2020-09-24 11:21 ` Daniel Henrique Barboza
2020-09-24 11:32 ` Greg Kurz
2020-09-23 19:34 ` [PATCH 6/6] specs/ppc-spapr-numa: update with new NUMA support Daniel Henrique Barboza
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=20200923193458.203186-1-danielhb413@gmail.com \
--to=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--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).