qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: "Daniel Henrique Barboza" <danielhb413@gmail.com>,
	"Joel Stanley" <joel@jms.id.au>,
	"Cédric Le Goater" <clg@kaod.org>,
	"Nicholas Piggin" <npiggin@gmail.com>,
	"Frédéric Barrat" <fbarrat@linux.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: [PATCH v2 0/2] ppc/pnv: Set P10 core xscom region size to match hardware
Date: Thu,  6 Jul 2023 15:39:21 +1000	[thread overview]
Message-ID: <20230706053923.115003-1-npiggin@gmail.com> (raw)

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(-)

-- 
2.40.1



             reply	other threads:[~2023-07-06  5:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06  5:39 Nicholas Piggin [this message]
2023-07-06  5:39 ` [PATCH v2 1/2] ppc/pnv: Set P10 core xscom region size to match hardware 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

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=20230706053923.115003-1-npiggin@gmail.com \
    --to=npiggin@gmail.com \
    --cc=clg@kaod.org \
    --cc=danielhb413@gmail.com \
    --cc=fbarrat@linux.ibm.com \
    --cc=joel@jms.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).