From: "Cédric Le Goater" <clg@kaod.org>
To: Daniel Henrique Barboza <danielhb413@gmail.com>, <qemu-devel@nongnu.org>
Cc: <qemu-ppc@nongnu.org>, Frederic Barrat <fbarrat@linux.ibm.com>
Subject: Re: [PATCH for-7.2 02/10] ppc/pnv: add phb-id/chip-id PnvPHB4RootBus properties
Date: Wed, 3 Aug 2022 18:22:36 +0200 [thread overview]
Message-ID: <aa2ba31d-310c-fbb0-b4da-3b8da02d8201@kaod.org> (raw)
In-Reply-To: <20220803134459.2633902-3-danielhb413@gmail.com>
On 8/3/22 15:44, Daniel Henrique Barboza wrote:
> The same rationale provided in the PHB3 bus case applies here.
>
> Note: we could have merged both buses in a single object, like we did
> with the root ports, and spare some boilerplate. The reason we opted to
> preserve both buses objects is twofold:
>
> - there's not user side advantage in doing so. Unifying the root ports
> presents a clear user QOL change when we enable user created devices back.
> The buses objects, aside from having a different QOM name, is transparent
> to the user;
>
> - we leave a door opened in case we want to increase the root port limit
> for phb4/5 later on without having to deal with phb3 code.
>
> Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Thanks,
C.
> ---
> hw/pci-host/pnv_phb4.c | 51 ++++++++++++++++++++++++++++++++++
> include/hw/pci-host/pnv_phb4.h | 10 +++++++
> 2 files changed, 61 insertions(+)
>
> diff --git a/hw/pci-host/pnv_phb4.c b/hw/pci-host/pnv_phb4.c
> index b98c394713..824e1a73fb 100644
> --- a/hw/pci-host/pnv_phb4.c
> +++ b/hw/pci-host/pnv_phb4.c
> @@ -1551,6 +1551,12 @@ void pnv_phb4_bus_init(DeviceState *dev, PnvPHB4 *phb)
> pnv_phb4_set_irq, pnv_phb4_map_irq, phb,
> &phb->pci_mmio, &phb->pci_io,
> 0, 4, TYPE_PNV_PHB4_ROOT_BUS);
> +
> + object_property_set_int(OBJECT(pci->bus), "phb-id", phb->phb_id,
> + &error_abort);
> + object_property_set_int(OBJECT(pci->bus), "chip-id", phb->chip_id,
> + &error_abort);
> +
> pci_setup_iommu(pci->bus, pnv_phb4_dma_iommu, phb);
> pci->bus->flags |= PCI_BUS_EXTENDED_CONFIG_SPACE;
> }
> @@ -1708,10 +1714,55 @@ static const TypeInfo pnv_phb5_type_info = {
> .instance_size = sizeof(PnvPHB4),
> };
>
> +static void pnv_phb4_root_bus_get_prop(Object *obj, Visitor *v,
> + const char *name,
> + void *opaque, Error **errp)
> +{
> + PnvPHB4RootBus *bus = PNV_PHB4_ROOT_BUS(obj);
> + uint64_t value = 0;
> +
> + if (strcmp(name, "phb-id") == 0) {
> + value = bus->phb_id;
> + } else {
> + value = bus->chip_id;
> + }
> +
> + visit_type_size(v, name, &value, errp);
> +}
> +
> +static void pnv_phb4_root_bus_set_prop(Object *obj, Visitor *v,
> + const char *name,
> + void *opaque, Error **errp)
> +
> +{
> + PnvPHB4RootBus *bus = PNV_PHB4_ROOT_BUS(obj);
> + uint64_t value;
> +
> + if (!visit_type_size(v, name, &value, errp)) {
> + return;
> + }
> +
> + if (strcmp(name, "phb-id") == 0) {
> + bus->phb_id = value;
> + } else {
> + bus->chip_id = value;
> + }
> +}
> +
> static void pnv_phb4_root_bus_class_init(ObjectClass *klass, void *data)
> {
> BusClass *k = BUS_CLASS(klass);
>
> + object_class_property_add(klass, "phb-id", "int",
> + pnv_phb4_root_bus_get_prop,
> + pnv_phb4_root_bus_set_prop,
> + NULL, NULL);
> +
> + object_class_property_add(klass, "chip-id", "int",
> + pnv_phb4_root_bus_get_prop,
> + pnv_phb4_root_bus_set_prop,
> + NULL, NULL);
> +
> /*
> * PHB4 has only a single root complex. Enforce the limit on the
> * parent bus
> diff --git a/include/hw/pci-host/pnv_phb4.h b/include/hw/pci-host/pnv_phb4.h
> index 20aa4819d3..50d4faa001 100644
> --- a/include/hw/pci-host/pnv_phb4.h
> +++ b/include/hw/pci-host/pnv_phb4.h
> @@ -45,7 +45,17 @@ typedef struct PnvPhb4DMASpace {
> QLIST_ENTRY(PnvPhb4DMASpace) list;
> } PnvPhb4DMASpace;
>
> +/*
> + * PHB4 PCIe Root Bus
> + */
> #define TYPE_PNV_PHB4_ROOT_BUS "pnv-phb4-root"
> +struct PnvPHB4RootBus {
> + PCIBus parent;
> +
> + uint32_t chip_id;
> + uint32_t phb_id;
> +};
> +OBJECT_DECLARE_SIMPLE_TYPE(PnvPHB4RootBus, PNV_PHB4_ROOT_BUS)
>
> /*
> * PHB4 PCIe Host Bridge for PowerNV machines (POWER9)
next prev parent reply other threads:[~2022-08-03 16:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 13:44 [PATCH for-7.2 00/10] enable pnv-phb user created devices Daniel Henrique Barboza
2022-08-03 13:44 ` [PATCH for-7.2 01/10] ppc/pnv: add phb-id/chip-id PnvPHB3RootBus properties Daniel Henrique Barboza
2022-08-03 16:22 ` Cédric Le Goater
2022-08-03 13:44 ` [PATCH for-7.2 02/10] ppc/pnv: add phb-id/chip-id PnvPHB4RootBus properties Daniel Henrique Barboza
2022-08-03 16:22 ` Cédric Le Goater [this message]
2022-08-03 13:44 ` [PATCH for-7.2 03/10] ppc/pnv: set root port chassis and slot using Bus properties Daniel Henrique Barboza
2022-08-03 16:25 ` Cédric Le Goater
2022-08-03 13:44 ` [PATCH for-7.2 04/10] ppc/pnv: add helpers for pnv-phb user devices Daniel Henrique Barboza
2022-08-05 10:41 ` Frederic Barrat
2022-08-08 11:04 ` Daniel Henrique Barboza
2022-08-03 13:44 ` [PATCH for-7.2 05/10] ppc/pnv: turn chip8->phbs[] into a PnvPHB* array Daniel Henrique Barboza
2022-08-03 13:44 ` [PATCH for-7.2 06/10] ppc/pnv: enable user created pnv-phb for powernv8 Daniel Henrique Barboza
2022-08-05 10:50 ` Frederic Barrat
2022-08-08 16:50 ` Daniel Henrique Barboza
2022-08-08 23:30 ` Daniel Henrique Barboza
2022-08-03 13:44 ` [PATCH for-7.2 07/10] ppc/pnv: add PHB4 helpers for user created pnv-phb Daniel Henrique Barboza
2022-08-03 13:44 ` [PATCH for-7.2 08/10] ppc/pnv: enable user created pnv-phb powernv9 Daniel Henrique Barboza
2022-08-03 13:44 ` [PATCH for-7.2 09/10] ppc/pnv: change pnv_phb4_get_pec() to also retrieve chip10->pecs Daniel Henrique Barboza
2022-08-03 13:44 ` [PATCH for-7.2 10/10] ppc/pnv: user creatable pnv-phb for powernv10 Daniel Henrique Barboza
2022-08-05 11:06 ` [PATCH for-7.2 00/10] enable pnv-phb user created devices Frederic Barrat
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=aa2ba31d-310c-fbb0-b4da-3b8da02d8201@kaod.org \
--to=clg@kaod.org \
--cc=danielhb413@gmail.com \
--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).