From: "Cédric Le Goater" <clg@kaod.org>
To: <qemu-ppc@nongnu.org>, <qemu-devel@nongnu.org>
Cc: Frederic Barrat <fbarrat@linux.ibm.com>,
Daniel Henrique Barboza <danielhb413@gmail.com>,
Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH v2 00/19] ppc/pnv: Add support for user created PHB3/PHB4 devices
Date: Wed, 15 Dec 2021 17:56:29 +0100 [thread overview]
Message-ID: <8cc4ad78-48e9-5e01-cae8-d89f9ee8a3a1@kaod.org> (raw)
In-Reply-To: <20211213132830.108372-1-clg@kaod.org>
On 12/13/21 14:28, Cédric Le Goater wrote:
> Hello,
>
> On the POWER8 processor, powernv8 machine, PHB3 devices can simply be
> created with :
>
> -device pnv-phb3,chip-id=0,index=1
>
> with a maximum of 3 PHB3s per chip, each PHB3 adding a new PCIe bus.
>
> On the POWER9 processor, powernv9 machine, the logic is different. The
> the chip comes with 3 PHB4 PECs (PCI Express Controller) and each PEC
> can have several PHBs :
>
> * PEC0 provides 1 PHB (PHB0)
> * PEC1 provides 2 PHBs (PHB1 and PHB2)
> * PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
>
> The PEC devices can be created with :
>
> -device pnv-phb4-pec,chip-id=0,index=1
>
> And the number of added PHB4 devices depends on the PEC index. Each
> PHB4 adds a new PCIe bus.
>
> The following changes are mostly cleanups and improvements of the
> PHB3/4 realize routines to enable support. One important change is
> related to the way the powernv machine populates the device tree. It
> depends on the object hierarchy and it is necessary to reparent user
> created devices to the chip they belong to (see PATCH 5). PHB3 is a
> little more sophisticated because of its SysBusDevice nature (see
> PATCH 6).
>
> It would be preferable for libvirt and user to add one PHB4 (one PCIe
> bus) at a time but that's another step. The plan is to merge real soon
> the first patches which are required cleanups of the models and give
> some more time for the last ones.
Applied patches 1-14 which are simple cleanups to ppc-next.
Thanks,
C.
next prev parent reply other threads:[~2021-12-15 17:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 13:28 [PATCH v2 00/19] ppc/pnv: Add support for user created PHB3/PHB4 devices Cédric Le Goater
2021-12-13 13:28 ` [PATCH v2 01/19] ppc/pnv: Change the maximum of PHB3 devices for Power8NVL Cédric Le Goater
2021-12-13 18:30 ` Daniel Henrique Barboza
2021-12-13 13:28 ` [PATCH v2 02/19] ppc/pnv: Introduce a "chip" property under PHB3 Cédric Le Goater
2021-12-13 13:28 ` [PATCH v2 03/19] ppc/pnv: Use the chip class to check the index of PHB3 devices Cédric Le Goater
2021-12-13 18:33 ` Daniel Henrique Barboza
2021-12-13 13:28 ` [PATCH v2 04/19] ppc/pnv: Drop the "num-phbs" property Cédric Le Goater
2021-12-13 13:28 ` [PATCH v2 05/19] ppc/pnv: Move mapping of the PHB3 CQ regions under pnv_pbcq_realize() Cédric Le Goater
2021-12-13 13:28 ` [PATCH v2 06/19] ppc/pnv: Use QOM hierarchy to scan PHB3 devices Cédric Le Goater
2021-12-13 18:37 ` Daniel Henrique Barboza
2021-12-13 13:28 ` [PATCH v2 07/19] ppc/pnv: Introduce a num_pecs class attribute for PHB4 PEC devices Cédric Le Goater
2021-12-13 13:28 ` [PATCH v2 08/19] ppc/pnv: Introduce version and device_id class atributes for PHB4 devices Cédric Le Goater
2021-12-13 13:28 ` [PATCH v2 09/19] ppc/pnv: Introduce a "chip" property under the PHB4 model Cédric Le Goater
2021-12-13 13:28 ` [PATCH v2 10/19] ppc/pnv: Introduce a num_stack class attribute Cédric Le Goater
2021-12-13 13:28 ` [PATCH v2 11/19] ppc/pnv: Compute the PHB index from the PHB4 PEC model Cédric Le Goater
2021-12-13 13:28 ` [PATCH v2 12/19] ppc/pnv: Remove "system-memory" property from PHB4 PEC Cédric Le Goater
2021-12-13 13:28 ` [PATCH v2 13/19] ppc/pnv: Move realize of PEC stacks under the PEC model Cédric Le Goater
2021-12-13 13:28 ` [PATCH v2 14/19] ppc/pnv: Use QOM hierarchy to scan PEC PHB4 devices Cédric Le Goater
2021-12-13 18:39 ` Daniel Henrique Barboza
2021-12-13 13:28 ` [PATCH v2 15/19] ppc/pnv: Introduce support for user created PHB3 devices Cédric Le Goater
2021-12-13 13:28 ` [PATCH v2 16/19] ppc/pnv: Reparent user created PHB3 devices to the PnvChip Cédric Le Goater
2021-12-13 13:28 ` [PATCH v2 17/19] ppc/pnv: Complete user created PHB3 devices Cédric Le Goater
2021-12-13 13:28 ` [PATCH v2 18/19] ppc/pnv: Introduce support for user created PHB4 devices Cédric Le Goater
2021-12-13 13:28 ` [PATCH v2 19/19] ppc/pnv: Move num_phbs under Pnv8Chip Cédric Le Goater
2022-01-04 9:53 ` Daniel Henrique Barboza
2022-01-04 10:07 ` Cédric Le Goater
2021-12-15 16:56 ` Cédric Le Goater [this message]
2022-01-04 9:56 ` [PATCH v2 00/19] ppc/pnv: Add support for user created PHB3/PHB4 devices Daniel Henrique Barboza
2022-01-04 10:07 ` 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=8cc4ad78-48e9-5e01-cae8-d89f9ee8a3a1@kaod.org \
--to=clg@kaod.org \
--cc=danielhb413@gmail.com \
--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).