From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: "Nicholas Piggin" <npiggin@gmail.com>,
"Joel Stanley" <joel@jms.id.au>,
"Cédric Le Goater" <clg@kaod.org>,
"Frédéric Barrat" <fbarrat@linux.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [PATCH v2 0/2] ppc/pnv: Set P10 core xscom region size to match hardware
Date: Fri, 7 Jul 2023 04:20:13 -0300 [thread overview]
Message-ID: <e16f68a3-4d8f-4200-b9ef-131bcdd13db1@gmail.com> (raw)
In-Reply-To: <20230706053923.115003-1-npiggin@gmail.com>
Queued in gitlab.com/danielhb/qemu/tree/ppc-next. Thanks,
Daniel
On 7/6/23 02:39, Nicholas Piggin wrote:
> Sorry about the paper bag bug in the first version of the patch -
> I broke powernv8 and 9.
>
> This adds a xsom_size core class field to change the P10 size without
> changing the others.
>
> Also added a P10 xscom test, and passes make check.
>
> Thanks,
> Nick
>
> Nicholas Piggin (2):
> ppc/pnv: Set P10 core xscom region size to match hardware
> tests/qtest: Add xscom tests for powernv10 machine
>
> hw/ppc/pnv_core.c | 6 +++--
> include/hw/ppc/pnv_core.h | 1 +
> include/hw/ppc/pnv_xscom.h | 2 +-
> tests/qtest/pnv-xscom-test.c | 44 ++++++++++++++++++++++++++++--------
> 4 files changed, 41 insertions(+), 12 deletions(-)
>
prev parent reply other threads:[~2023-07-07 7:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 5:39 [PATCH v2 0/2] ppc/pnv: Set P10 core xscom region size to match hardware Nicholas Piggin
2023-07-06 5:39 ` [PATCH v2 1/2] " Nicholas Piggin
2023-07-06 5:39 ` [PATCH v2 2/2] tests/qtest: Add xscom tests for powernv10 machine Nicholas Piggin
2023-07-06 6:21 ` [PATCH v2 0/2] ppc/pnv: Set P10 core xscom region size to match hardware Cédric Le Goater
2023-07-06 7:19 ` Cédric Le Goater
2023-07-07 7:20 ` 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=e16f68a3-4d8f-4200-b9ef-131bcdd13db1@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--cc=fbarrat@linux.ibm.com \
--cc=joel@jms.id.au \
--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).