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 07/14] ppc/pnv: Introduce a num_pecs class attribute for PHB4 PEC devices
Date: Thu, 2 Dec 2021 14:34:50 -0300 [thread overview]
Message-ID: <74b438b4-3800-7266-18ba-6b9ab9a9add4@gmail.com> (raw)
In-Reply-To: <20211202144235.1276352-8-clg@kaod.org>
On 12/2/21 11:42, Cédric Le Goater wrote:
> POWER9 processor 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)
>
> A num_pecs class attribute represents better the logic units of the
> POWER9 chip. Use that instead of num_phbs which fits POWER8 chips.
> This will ease adding support for user created devices.
>
> Signed-off-by: Cédric Le Goater <clg@kaod.org>
> ---
Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
> include/hw/ppc/pnv.h | 2 ++
> hw/ppc/pnv.c | 20 +++++++++-----------
> 2 files changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/include/hw/ppc/pnv.h b/include/hw/ppc/pnv.h
> index 247379ef1f88..f2c238062f4a 100644
> --- a/include/hw/ppc/pnv.h
> +++ b/include/hw/ppc/pnv.h
> @@ -53,6 +53,7 @@ struct PnvChip {
> PnvCore **cores;
>
> uint32_t num_phbs;
> + uint32_t num_pecs;
>
> MemoryRegion xscom_mmio;
> MemoryRegion xscom;
> @@ -136,6 +137,7 @@ struct PnvChipClass {
> uint64_t chip_cfam_id;
> uint64_t cores_mask;
> uint32_t num_phbs;
> + uint32_t num_pecs;
>
> DeviceRealize parent_realize;
>
> diff --git a/hw/ppc/pnv.c b/hw/ppc/pnv.c
> index 45d8ecbf2bf7..185464a1d443 100644
> --- a/hw/ppc/pnv.c
> +++ b/hw/ppc/pnv.c
> @@ -658,7 +658,7 @@ static void pnv_chip_power9_pic_print_info(PnvChip *chip, Monitor *mon)
> pnv_xive_pic_print_info(&chip9->xive, mon);
> pnv_psi_pic_print_info(&chip9->psi, mon);
>
> - for (i = 0; i < PNV9_CHIP_MAX_PEC; i++) {
> + for (i = 0; i < chip->num_pecs; i++) {
> PnvPhb4PecState *pec = &chip9->pecs[i];
> for (j = 0; j < pec->num_stacks; j++) {
> pnv_phb4_pic_print_info(&pec->stacks[j].phb, mon);
> @@ -1330,15 +1330,14 @@ static void pnv_chip_power9_instance_init(Object *obj)
>
> object_initialize_child(obj, "homer", &chip9->homer, TYPE_PNV9_HOMER);
>
> - for (i = 0; i < PNV9_CHIP_MAX_PEC; i++) {
> + if (defaults_enabled()) {
> + chip->num_pecs = pcc->num_pecs;
> + }
> +
> + for (i = 0; i < chip->num_pecs; i++) {
> object_initialize_child(obj, "pec[*]", &chip9->pecs[i],
> TYPE_PNV_PHB4_PEC);
> }
> -
> - /*
> - * Number of PHBs is the chip default
> - */
> - chip->num_phbs = pcc->num_phbs;
> }
>
> static void pnv_chip_quad_realize(Pnv9Chip *chip9, Error **errp)
> @@ -1374,7 +1373,7 @@ static void pnv_chip_power9_phb_realize(PnvChip *chip, Error **errp)
> int i, j;
> int phb_id = 0;
>
> - for (i = 0; i < PNV9_CHIP_MAX_PEC; i++) {
> + for (i = 0; i < chip->num_pecs; i++) {
> PnvPhb4PecState *pec = &chip9->pecs[i];
> PnvPhb4PecClass *pecc = PNV_PHB4_PEC_GET_CLASS(pec);
> uint32_t pec_nest_base;
> @@ -1402,8 +1401,7 @@ static void pnv_chip_power9_phb_realize(PnvChip *chip, Error **errp)
> pnv_xscom_add_subregion(chip, pec_nest_base, &pec->nest_regs_mr);
> pnv_xscom_add_subregion(chip, pec_pci_base, &pec->pci_regs_mr);
>
> - for (j = 0; j < pec->num_stacks && phb_id < chip->num_phbs;
> - j++, phb_id++) {
> + for (j = 0; j < pec->num_stacks; j++, phb_id++) {
> PnvPhb4PecStack *stack = &pec->stacks[j];
> Object *obj = OBJECT(&stack->phb);
>
> @@ -1559,7 +1557,7 @@ static void pnv_chip_power9_class_init(ObjectClass *klass, void *data)
> k->xscom_core_base = pnv_chip_power9_xscom_core_base;
> k->xscom_pcba = pnv_chip_power9_xscom_pcba;
> dc->desc = "PowerNV Chip POWER9";
> - k->num_phbs = 6;
> + k->num_pecs = PNV9_CHIP_MAX_PEC;
>
> device_class_set_parent_realize(dc, pnv_chip_power9_realize,
> &k->parent_realize);
>
next prev parent reply other threads:[~2021-12-02 17:38 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
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 [this message]
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=74b438b4-3800-7266-18ba-6b9ab9a9add4@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).