From: Chalapathi V <chalapathi.v@linux.ibm.com>
To: qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, fbarrat@linux.ibm.com, npiggin@gmail.com,
clg@kaod.org, calebs@us.ibm.com, chalapathi.v@ibm.com,
chalapathi.v@linux.ibm.com, saif.abrar@linux.vnet.ibm.com
Subject: [PATCH v8 0/3] pnv N1 chiplet model
Date: Fri, 8 Dec 2023 09:19:44 -0600 [thread overview]
Message-ID: <20231208151947.26951-1-chalapathi.v@linux.ibm.com> (raw)
Hello,
Thank you for the review and suggestions on V7.
There are no major design/logic changes done in revision 8 from revision 7.
Addressed the minor comments.
The qom-tree looks like below.
(qemu) info qom-tree
/machine (powernv10-machine)
/chip[0] (power10_v2.0-pnv-chip)
/n1-chiplet (pnv-N1-chiplet)
/nest-pervasive-common (pnv-nest-chiplet-pervasive)
/pervasive-control[0] (memory-region)
/xscom-n1-chiplet-pb-scom-eq[0] (memory-region)
/xscom-n1-chiplet-pb-scom-es[0] (memory-region)
Patches overview in V8.
PATCH1: Create a common nest pervasive chiplet model with control chiplet scom
registers.
PATCH2: Create a N1 chiplet model and implement powerbus scom registers.
Connect common nest pervasive model to N1 chiplet model to define
chiplet control scoms for N1 chiplet.
PATCH3: Connect N1 chiplet model to p10 chip.
Test covered:
Ran make check && make check-avocado and found no obvious issues.
Thank You,
Chalapathi
Chalapathi V (3):
hw/ppc: Add pnv nest pervasive common chiplet model
hw/ppc: Add N1 chiplet model
hw/ppc: N1 chiplet wiring
include/hw/ppc/pnv_chip.h | 2 +
include/hw/ppc/pnv_n1_chiplet.h | 32 +++++
include/hw/ppc/pnv_nest_pervasive.h | 32 +++++
include/hw/ppc/pnv_xscom.h | 9 ++
hw/ppc/pnv.c | 15 ++
hw/ppc/pnv_n1_chiplet.c | 173 +++++++++++++++++++++++
hw/ppc/pnv_nest_pervasive.c | 208 ++++++++++++++++++++++++++++
hw/ppc/meson.build | 2 +
8 files changed, 473 insertions(+)
create mode 100644 include/hw/ppc/pnv_n1_chiplet.h
create mode 100644 include/hw/ppc/pnv_nest_pervasive.h
create mode 100644 hw/ppc/pnv_n1_chiplet.c
create mode 100644 hw/ppc/pnv_nest_pervasive.c
--
2.31.1
next reply other threads:[~2023-12-08 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 15:19 Chalapathi V [this message]
2023-12-08 15:19 ` [PATCH v8 1/3] hw/ppc: Add pnv nest pervasive common chiplet model Chalapathi V
2023-12-12 9:40 ` Cédric Le Goater
2023-12-08 15:19 ` [PATCH v8 2/3] hw/ppc: Add N1 " Chalapathi V
2023-12-12 9:41 ` Cédric Le Goater
2023-12-08 15:19 ` [PATCH v8 3/3] hw/ppc: N1 chiplet wiring Chalapathi V
2023-12-12 9:42 ` Cédric Le Goater
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=20231208151947.26951-1-chalapathi.v@linux.ibm.com \
--to=chalapathi.v@linux.ibm.com \
--cc=calebs@us.ibm.com \
--cc=chalapathi.v@ibm.com \
--cc=clg@kaod.org \
--cc=fbarrat@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=saif.abrar@linux.vnet.ibm.com \
/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).