From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: "Cédric Le Goater" <clg@kaod.org>,
"Frédéric Barrat" <fbarrat@linux.ibm.com>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Greg Kurz" <groug@kaod.org>,
"Harsh Prateek Bora" <harshpb@linux.ibm.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 0/4] ppc/pnv: SMT support for powernv
Date: Wed, 5 Jul 2023 14:04:02 -0300 [thread overview]
Message-ID: <6e54457b-face-25fe-1df8-f70c0a962610@gmail.com> (raw)
In-Reply-To: <20230705120631.27670-1-npiggin@gmail.com>
Queued in gitlab.com/danielhb/qemu/tree/ppc-next. Thanks,
Daniel
On 7/5/23 09:06, Nicholas Piggin wrote:
> These patches implement enough to install a distro, boot, run SMP KVM
> guests with libvirt with good performance using MTTCG (as reported by
> Cedric).
>
> There are a few more SPRs that need to be done, and per-LPAR SPRs are
> mostly not annotated yet so it can't run in 1 LPAR mode. But those can
> be added in time, it will take a bit of time to get everything exactly
> as hardware does so I consider this good enough to run common
> software usefully.
>
> Since RFC:
> - Rebased against ppc-next (no conflicts vs upstream anyway).
> - Add patch 4 avocado boot test with SMT, as was added with pseries SMT.
> - Renamed POWERPC_FLAG_1LPAR to POWERPC_FLAG_SMT_1LPAR since it implies
> SMT.
> - Fixed typos, patch 1, 3 changelogs improvement (hopefully).
>
> Since v1:
> - Fix clang compile bug
> - Fix LPAR-per-thread bug in CTRL/DPDES/msgsndp in patch 1
> - Add 2-socket test case to powernv Linux boot avocado test
> - Remove SMT caveat from docs/system/ppc/powernv.rst
>
> Thanks,
> Nick
>
> Nicholas Piggin (4):
> target/ppc: Add LPAR-per-core vs per-thread mode flag
> target/ppc: SMT support for the HID SPR
> ppc/pnv: SMT support for powernv
> tests/avocado: Add powernv machine test script
>
> docs/system/ppc/powernv.rst | 5 ---
> hw/ppc/pnv.c | 12 +++++
> hw/ppc/pnv_core.c | 13 +++---
> hw/ppc/spapr_cpu_core.c | 2 +
> target/ppc/cpu.h | 3 ++
> target/ppc/cpu_init.c | 14 +++++-
> target/ppc/excp_helper.c | 4 ++
> target/ppc/helper.h | 1 +
> target/ppc/misc_helper.c | 29 ++++++++++++
> target/ppc/spr_common.h | 1 +
> target/ppc/translate.c | 27 ++++++++---
> tests/avocado/ppc_powernv.py | 87 ++++++++++++++++++++++++++++++++++++
> 12 files changed, 179 insertions(+), 19 deletions(-)
> create mode 100644 tests/avocado/ppc_powernv.py
>
prev parent reply other threads:[~2023-07-05 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 12:06 [PATCH v2 0/4] ppc/pnv: SMT support for powernv Nicholas Piggin
2023-07-05 12:06 ` [PATCH v2 1/4] target/ppc: Add LPAR-per-core vs per-thread mode flag Nicholas Piggin
2023-07-05 12:06 ` [PATCH v2 2/4] target/ppc: SMT support for the HID SPR Nicholas Piggin
2023-07-05 12:06 ` [PATCH v2 3/4] ppc/pnv: SMT support for powernv Nicholas Piggin
2023-07-05 12:06 ` [PATCH v2 4/4] tests/avocado: Add powernv machine test script Nicholas Piggin
2023-07-05 14:28 ` Cédric Le Goater
2023-07-05 17:04 ` Daniel Henrique Barboza [this message]
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=6e54457b-face-25fe-1df8-f70c0a962610@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=fbarrat@linux.ibm.com \
--cc=groug@kaod.org \
--cc=harshpb@linux.ibm.com \
--cc=npiggin@gmail.com \
--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).