From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, clg@kaod.org, fbarrat@linux.ibm.com,
Daniel Henrique Barboza <danielhb413@gmail.com>
Subject: [PATCH 00/10] enable pnv-phb user created devices
Date: Fri, 8 Jul 2022 10:25:12 -0300 [thread overview]
Message-ID: <20220708132522.581382-1-danielhb413@gmail.com> (raw)
This series is built on top of
"[PATCH v3 00/12] powernv: introduce pnv-phb base/proxy devices" [1]
that is under review in [1]. I'm sending this last part of the pnv-phb
rework to allow everyone to see what's the endgame I'm planning with
this work.
The main differences between the approach taken here, versus the approach
made by "[PATCH v2 00/16] powernv: introduce pnv-phb base/proxy
devices" [2], is:
- the Root Buses objects are now inheriting phb-id and chip-id. This
turned out to be a clean way of keeping the code QOM compliant, without
having to do things like dev->parent_bus->parent. All the attributes
that the root port needs are found in its bus parent;
- the logic exclusive to user created devices is all centered in a
single helper inside pnv-phb realize(). PHB3/PHB4 realize() are
oblivious to whether the device is user created or not. I believe this
approach is clearer than what I was doing before.
I'll respin/rebase this patches depending on the amount of changes
we have during the pnv-phb proxy device review.
[1] https://lists.gnu.org/archive/html/qemu-devel/2022-06/msg04347.html
[2] https://lists.gnu.org/archive/html/qemu-devel/2022-05/msg06254.html
Daniel Henrique Barboza (10):
ppc/pnv: add phb-id/chip-id PnvPHB3RootBus properties
ppc/pnv: add phb-id/chip-id PnvPHB4RootBus properties
ppc/pnv: set root port chassis and slot using Bus properties
ppc/pnv: add helpers for pnv-phb user devices
ppc/pnv: turn chip8->phbs[] into a PnvPHB* array
ppc/pnv: enable user created pnv-phb for powernv8
ppc/pnv: add PHB4 helpers for user created pnv-phb
ppc/pnv: enable user created pnv-phb powernv9
ppc/pnv: change pnv_phb4_get_pec() to also retrieve chip10->pecs
ppc/pnv: user creatable pnv-phb for powernv10
hw/pci-host/pnv_phb.c | 166 ++++++++++++++++++++++++++++++---
hw/pci-host/pnv_phb3.c | 50 ++++++++++
hw/pci-host/pnv_phb4.c | 51 ++++++++++
hw/pci-host/pnv_phb4_pec.c | 6 +-
hw/ppc/pnv.c | 30 +++++-
include/hw/pci-host/pnv_phb3.h | 9 +-
include/hw/pci-host/pnv_phb4.h | 10 ++
include/hw/ppc/pnv.h | 6 +-
8 files changed, 308 insertions(+), 20 deletions(-)
--
2.36.1
next reply other threads:[~2022-07-08 13:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 13:25 Daniel Henrique Barboza [this message]
2022-07-08 13:25 ` [PATCH 01/10] ppc/pnv: add phb-id/chip-id PnvPHB3RootBus properties Daniel Henrique Barboza
2022-07-08 13:25 ` [PATCH 02/10] ppc/pnv: add phb-id/chip-id PnvPHB4RootBus properties Daniel Henrique Barboza
2022-07-08 13:25 ` [PATCH 03/10] ppc/pnv: set root port chassis and slot using Bus properties Daniel Henrique Barboza
2022-07-08 13:25 ` [PATCH 04/10] ppc/pnv: add helpers for pnv-phb user devices Daniel Henrique Barboza
2022-07-08 13:25 ` [PATCH 05/10] ppc/pnv: turn chip8->phbs[] into a PnvPHB* array Daniel Henrique Barboza
2022-07-08 13:25 ` [PATCH 06/10] ppc/pnv: enable user created pnv-phb for powernv8 Daniel Henrique Barboza
2022-07-08 13:25 ` [PATCH 07/10] ppc/pnv: add PHB4 helpers for user created pnv-phb Daniel Henrique Barboza
2022-07-08 13:25 ` [PATCH 08/10] ppc/pnv: enable user created pnv-phb powernv9 Daniel Henrique Barboza
2022-07-08 13:25 ` [PATCH 09/10] ppc/pnv: change pnv_phb4_get_pec() to also retrieve chip10->pecs Daniel Henrique Barboza
2022-07-08 13:25 ` [PATCH 10/10] ppc/pnv: user creatable pnv-phb for powernv10 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=20220708132522.581382-1-danielhb413@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--cc=fbarrat@linux.ibm.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).