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 v5 0/4] pSeries FORM2 affinity support
Date: Mon, 6 Sep 2021 21:25:23 -0300 [thread overview]
Message-ID: <20210907002527.412013-1-danielhb413@gmail.com> (raw)
Hi,
In this new version, the biggest change is that now we're initializing
NUMA associativity internal data during machine_reset(), instead of
machine_init(), to allow for the guest to switch between FORM1 and
FORM2 during guest reset. All other changes are consequence of this
design change.
Changes from v4:
- former patch 1:
* dropped, pseries-6.2 machine type is already available
- new patch 1:
* move numa associativity init to machine reset
- patch 3:
* avoid resetting associativity data if FORM1 was chosen
- former patch 4:
* dropped, folded into patch 1
- patch 4 (former 5):
* move both FORM1 verifications to post-CAS
- v4 link: https://lists.gnu.org/archive/html/qemu-devel/2021-08/msg04860.html
Daniel Henrique Barboza (4):
spapr: move NUMA associativity init to machine reset
spapr_numa.c: split FORM1 code into helpers
spapr_numa.c: base FORM2 NUMA affinity support
spapr: move FORM1 verifications to do_client_architecture_support()
hw/ppc/spapr.c | 63 +++++-----
hw/ppc/spapr_hcall.c | 16 +++
hw/ppc/spapr_numa.c | 225 +++++++++++++++++++++++++++++++++---
include/hw/ppc/spapr.h | 1 +
include/hw/ppc/spapr_numa.h | 10 +-
include/hw/ppc/spapr_ovec.h | 1 +
6 files changed, 253 insertions(+), 63 deletions(-)
--
2.31.1
next reply other threads:[~2021-09-07 0:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 0:25 Daniel Henrique Barboza [this message]
2021-09-07 0:25 ` [PATCH v5 1/4] spapr: move NUMA associativity init to machine reset Daniel Henrique Barboza
2021-09-07 0:37 ` David Gibson
2021-09-07 7:10 ` Greg Kurz
2021-09-07 9:23 ` David Gibson
2021-09-10 19:57 ` Daniel Henrique Barboza
2021-09-11 3:53 ` David Gibson
2021-09-07 0:25 ` [PATCH v5 2/4] spapr_numa.c: split FORM1 code into helpers Daniel Henrique Barboza
2021-09-07 0:39 ` David Gibson
2021-09-07 0:25 ` [PATCH v5 3/4] spapr_numa.c: base FORM2 NUMA affinity support Daniel Henrique Barboza
2021-09-07 1:02 ` David Gibson
2021-09-07 10:07 ` Daniel Henrique Barboza
2021-09-08 1:54 ` David Gibson
2021-09-07 7:50 ` Greg Kurz
2021-09-07 0:25 ` [PATCH v5 4/4] spapr: move FORM1 verifications to do_client_architecture_support() Daniel Henrique Barboza
2021-09-07 1:04 ` 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=20210907002527.412013-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).