From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: "Cédric Le Goater" <clg@kaod.org>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Cc: Frederic Barrat <fbarrat@linux.ibm.com>, Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH 06/14] ppc/pnv: Complete user created PHB3 devices
Date: Thu, 2 Dec 2021 14:33:46 -0300 [thread overview]
Message-ID: <d630a7d7-bf99-8434-c197-f3301ae4bcd9@gmail.com> (raw)
In-Reply-To: <20211202144235.1276352-7-clg@kaod.org>
On 12/2/21 11:42, Cédric Le Goater wrote:
> PHB3s ared SysBus devices and should be allowed to be dynamically
> created.
>
> Signed-off-by: Cédric Le Goater <clg@kaod.org>
> ---
Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
> hw/pci-host/pnv_phb3.c | 9 +++++++++
> hw/ppc/pnv.c | 2 ++
> 2 files changed, 11 insertions(+)
>
> diff --git a/hw/pci-host/pnv_phb3.c b/hw/pci-host/pnv_phb3.c
> index e91f658b0060..b61f9c369f64 100644
> --- a/hw/pci-host/pnv_phb3.c
> +++ b/hw/pci-host/pnv_phb3.c
> @@ -1000,6 +1000,9 @@ static void pnv_phb3_realize(DeviceState *dev, Error **errp)
>
> /* User created devices */
> if (!phb->chip) {
> + Error *local_err = NULL;
> + BusState *s;
> +
> phb->chip = pnv_get_chip(pnv, phb->chip_id);
> if (!phb->chip) {
> error_setg(errp, "invalid chip id: %d", phb->chip_id);
> @@ -1011,6 +1014,12 @@ static void pnv_phb3_realize(DeviceState *dev, Error **errp)
> * correctly the device tree.
> */
> pnv_chip_parent_fixup(phb->chip, OBJECT(phb), phb->phb_id);
> +
> + s = qdev_get_parent_bus(DEVICE(phb->chip));
> + if (!qdev_set_parent_bus(DEVICE(phb), s, &local_err)) {
> + error_propagate(errp, local_err);
> + return;
> + }
> }
>
> /* LSI sources */
> diff --git a/hw/ppc/pnv.c b/hw/ppc/pnv.c
> index 9a458655efd9..45d8ecbf2bf7 100644
> --- a/hw/ppc/pnv.c
> +++ b/hw/ppc/pnv.c
> @@ -1927,6 +1927,8 @@ static void pnv_machine_power8_class_init(ObjectClass *oc, void *data)
>
> pmc->compat = compat;
> pmc->compat_size = sizeof(compat);
> +
> + machine_class_allow_dynamic_sysbus_dev(mc, TYPE_PNV_PHB3);
> }
>
> static void pnv_machine_power9_class_init(ObjectClass *oc, void *data)
>
next prev parent reply other threads:[~2021-12-02 17:35 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 14:42 [PATCH 00/14] ppc/pnv: Add support for user created PHB3/PHB4 devices Cédric Le Goater
2021-12-02 14:42 ` [PATCH 01/14] ppc/pnv: Reduce the maximum of PHB3 devices Cédric Le Goater
2021-12-02 17:27 ` Daniel Henrique Barboza
2021-12-02 17:34 ` Cédric Le Goater
2021-12-07 9:40 ` Frederic Barrat
2021-12-07 10:10 ` Cédric Le Goater
2021-12-02 14:42 ` [PATCH 02/14] ppc/pnv: Drop the "num-phbs" property Cédric Le Goater
2021-12-02 17:27 ` Daniel Henrique Barboza
2021-12-07 9:41 ` Frederic Barrat
2021-12-02 14:42 ` [PATCH 03/14] ppc/pnv: Move mapping of the PHB3 CQ regions under pnv_pbcq_realize() Cédric Le Goater
2021-12-02 17:29 ` Daniel Henrique Barboza
2021-12-07 9:41 ` Frederic Barrat
2021-12-02 14:42 ` [PATCH 04/14] ppc/pnv: Introduce support for user created PHB3 devices Cédric Le Goater
2021-12-02 17:31 ` Daniel Henrique Barboza
2021-12-07 9:47 ` Frederic Barrat
2021-12-07 10:17 ` Cédric Le Goater
2021-12-02 14:42 ` [PATCH 05/14] ppc/pnv: Reparent user created PHB3 devices to the PnvChip Cédric Le Goater
2021-12-02 17:32 ` Daniel Henrique Barboza
2021-12-07 9:51 ` Frederic Barrat
2021-12-02 14:42 ` [PATCH 06/14] ppc/pnv: Complete user created PHB3 devices Cédric Le Goater
2021-12-02 17:33 ` Daniel Henrique Barboza [this message]
2021-12-07 9:53 ` Frederic Barrat
2021-12-07 10:19 ` Cédric Le Goater
2021-12-02 14:42 ` [PATCH 07/14] ppc/pnv: Introduce a num_pecs class attribute for PHB4 PEC devices Cédric Le Goater
2021-12-02 17:34 ` Daniel Henrique Barboza
2021-12-07 10:00 ` Frederic Barrat
2021-12-07 10:45 ` Cédric Le Goater
2021-12-07 14:03 ` Frederic Barrat
2021-12-07 14:34 ` Cédric Le Goater
2021-12-02 14:42 ` [PATCH 08/14] ppc/pnv: Introduce version and device_id class atributes for PHB4 devices Cédric Le Goater
2021-12-02 17:37 ` Daniel Henrique Barboza
2021-12-07 10:01 ` Frederic Barrat
2021-12-07 10:21 ` Cédric Le Goater
2021-12-02 14:42 ` [PATCH 09/14] ppc/pnv: Introduce a "chip" property under the PHB4 model Cédric Le Goater
2021-12-02 17:37 ` Daniel Henrique Barboza
2021-12-07 10:01 ` Frederic Barrat
2021-12-02 14:42 ` [PATCH 10/14] ppc/pnv: Introduce a num_stack class attribute Cédric Le Goater
2021-12-02 17:44 ` Daniel Henrique Barboza
2021-12-07 10:04 ` Frederic Barrat
2021-12-02 14:42 ` [PATCH 11/14] ppc/pnv: Compute the PHB index from the PHB4 PEC model Cédric Le Goater
2021-12-02 17:47 ` Daniel Henrique Barboza
2021-12-07 10:06 ` Frederic Barrat
2021-12-07 10:24 ` Cédric Le Goater
2021-12-02 14:42 ` [PATCH 12/14] ppc/pnv: Remove "system-memory" property for he " Cédric Le Goater
2021-12-02 17:47 ` Daniel Henrique Barboza
2021-12-07 10:08 ` Frederic Barrat
2021-12-07 10:29 ` Cédric Le Goater
2021-12-07 10:11 ` Frederic Barrat
2021-12-02 14:42 ` [PATCH 13/14] ppc/pnv: Move realize of PEC stacks under the " Cédric Le Goater
2021-12-02 17:49 ` Daniel Henrique Barboza
2021-12-07 10:10 ` Frederic Barrat
2021-12-07 10:30 ` Cédric Le Goater
2021-12-02 14:42 ` [PATCH 14/14] ppc/pnv: Introduce support for user created PHB4 devices Cédric Le Goater
2021-12-02 17:49 ` Daniel Henrique Barboza
2021-12-07 10:12 ` 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=d630a7d7-bf99-8434-c197-f3301ae4bcd9@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--cc=fbarrat@linux.ibm.com \
--cc=groug@kaod.org \
--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).