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 v8 0/7] pSeries FORM2 affinity support
Date: Fri, 17 Sep 2021 18:27:55 -0300 [thread overview]
Message-ID: <20210917212802.424481-1-danielhb413@gmail.com> (raw)
Hi,
This new version contains changes made in patch 7 after looking more
carefully in the auto-generated NUMA node issue. I also took the
opportunity to make a change that Greg requested in an earlier
review that didn't make to v7.
Changes from v7:
- patch 3:
* removed redundant 'no FORM2 available yet' comments
- patch 7:
* removed the unneeded handling of numa_state->num_nodes
- v7 link: https://lists.gnu.org/archive/html/qemu-devel/2021-09/msg04156.html
Changes from v6:
- patch 1:
* added Greg's r-b
- patch 2:
* added the missing NUMA nodes number check
* added Greg's r-b
- patch 3 (former patch 4):
* no changes.
- former patch 3 (associativity_reset()): dropped
- patch 4 (new):
* added get_associativity()
* do not allocate FORM1_assoc_array in the heap
- patch 5:
* fixed typo
* added new check function to be called in CAS
- patch 6:
* do not allocate FORM2_assoc_array in the heap
- patch 7 (new):
* FORM2 fixes to handle the implicit added QEMU NUMA node when there's
no NUMA node added by the user.
- v6 link: https://lists.gnu.org/archive/html/qemu-devel/2021-09/msg02892.html
Daniel Henrique Barboza (7):
spapr_numa.c: split FORM1 code into helpers
spapr_numa.c: scrap 'legacy_numa' concept
spapr_numa.c: parametrize FORM1 macros
spapr_numa.c: rename numa_assoc_array to FORM1_assoc_array
spapr: move FORM1 verifications to post CAS
spapr_numa.c: FORM2 NUMA affinity support
spapr_numa.c: handle auto NUMA node with no distance info
hw/ppc/spapr.c | 41 +---
hw/ppc/spapr_hcall.c | 7 +
hw/ppc/spapr_numa.c | 380 ++++++++++++++++++++++++++++++------
include/hw/ppc/spapr.h | 35 ++--
include/hw/ppc/spapr_numa.h | 1 +
include/hw/ppc/spapr_ovec.h | 1 +
6 files changed, 354 insertions(+), 111 deletions(-)
--
2.31.1
next reply other threads:[~2021-09-17 21:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 21:27 Daniel Henrique Barboza [this message]
2021-09-17 21:27 ` [PATCH v8 1/7] spapr_numa.c: split FORM1 code into helpers Daniel Henrique Barboza
2021-09-17 21:27 ` [PATCH v8 2/7] spapr_numa.c: scrap 'legacy_numa' concept Daniel Henrique Barboza
2021-09-17 21:27 ` [PATCH v8 3/7] spapr_numa.c: parametrize FORM1 macros Daniel Henrique Barboza
2021-09-20 8:54 ` Greg Kurz
2021-09-17 21:27 ` [PATCH v8 4/7] spapr_numa.c: rename numa_assoc_array to FORM1_assoc_array Daniel Henrique Barboza
2021-09-20 9:21 ` Greg Kurz
2021-09-20 13:39 ` Daniel Henrique Barboza
2021-09-17 21:28 ` [PATCH v8 5/7] spapr: move FORM1 verifications to post CAS Daniel Henrique Barboza
2021-09-20 9:38 ` Greg Kurz
2021-09-17 21:28 ` [PATCH v8 6/7] spapr_numa.c: FORM2 NUMA affinity support Daniel Henrique Barboza
2021-09-20 15:10 ` Greg Kurz
2021-09-17 21:28 ` [PATCH v8 7/7] spapr_numa.c: handle auto NUMA node with no distance info Daniel Henrique Barboza
2021-09-20 15:22 ` Greg Kurz
2021-09-21 9:16 ` Igor Mammedov
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=20210917212802.424481-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).