From: "Cédric Le Goater" <clg@kaod.org>
To: Daniel Henrique Barboza <danielhb413@gmail.com>, <qemu-devel@nongnu.org>
Cc: qemu-ppc@nongnu.org, david@gibson.dropbear.id.au
Subject: Re: [PATCH v2 2/8] ppc/pnv: reduce stack->stack_no usage
Date: Mon, 17 Jan 2022 11:52:18 +0100 [thread overview]
Message-ID: <0f40f8a3-b27b-89d2-b52b-a64fe2705dbf@kaod.org> (raw)
In-Reply-To: <20220114180719.52117-3-danielhb413@gmail.com>
On 1/14/22 19:07, Daniel Henrique Barboza wrote:
> 'stack->stack_no' represents the order that a stack appears in its PEC.
> Its primary use is in XSCOM address space calculation in
> pnv_phb4_xscom_realize() when calculating the memory region offset.
>
> This attribute is redundant with phb->phb_id, which is calculated via
> pnv_phb4_pec_get_phb_id() using stack->stack_no information. It'll also
> be awkward to assign it when dealing with PECs and PHBs only in a future
> patch.
>
> A new pnv_phb4_get_phb_stack_no() helper is introduced to eliminate most
> of the stack->stack_no uses we have. The only use left after this patch
> is during pnv_pec_stk_default_phb_realize() when calculating phb_id,
> which will also handled in the next patches.
>
> 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 | 46 +++++++++++++++++++++++++++++++-----------
> 1 file changed, 34 insertions(+), 12 deletions(-)
>
> diff --git a/hw/pci-host/pnv_phb4.c b/hw/pci-host/pnv_phb4.c
> index 2658ef2d84..4933fe57fe 100644
> --- a/hw/pci-host/pnv_phb4.c
> +++ b/hw/pci-host/pnv_phb4.c
> @@ -868,6 +868,28 @@ static uint64_t pnv_pec_stk_nest_xscom_read(void *opaque, hwaddr addr,
> return phb->nest_regs[reg];
> }
>
> +/*
> + * Return the 'stack_no' of a PHB4. 'stack_no' is the order
> + * the PHB4 occupies in the PEC. This is the reverse of what
> + * pnv_phb4_pec_get_phb_id() does.
> + *
> + * E.g. a phb with phb_id = 4 and pec->index = 1 (PEC1) will
> + * be the second phb (stack_no = 1) of the PEC.
> + */
> +static int pnv_phb4_get_phb_stack_no(PnvPHB4 *phb)
> +{
> + PnvPhb4PecState *pec = phb->pec;
> + PnvPhb4PecClass *pecc = PNV_PHB4_PEC_GET_CLASS(pec);
> + int index = pec->index;
> + int stack_no = phb->phb_id;
> +
> + while (index--) {
> + stack_no -= pecc->num_stacks[index];
> + }
> +
> + return stack_no;
> +}
> +
> static void pnv_phb4_update_regions(PnvPHB4 *phb)
> {
> /* Unmap first always */
> @@ -894,10 +916,10 @@ static void pnv_phb4_update_regions(PnvPHB4 *phb)
>
> static void pnv_pec_stk_update_map(PnvPHB4 *phb)
> {
> - PnvPhb4PecStack *stack = phb->stack;
> PnvPhb4PecState *pec = phb->pec;
> MemoryRegion *sysmem = get_system_memory();
> uint64_t bar_en = phb->nest_regs[PEC_NEST_STK_BAR_EN];
> + int stack_no = pnv_phb4_get_phb_stack_no(phb);
> uint64_t bar, mask, size;
> char name[64];
>
> @@ -937,7 +959,7 @@ static void pnv_pec_stk_update_map(PnvPHB4 *phb)
> mask = phb->nest_regs[PEC_NEST_STK_MMIO_BAR0_MASK];
> size = ((~mask) >> 8) + 1;
> snprintf(name, sizeof(name), "pec-%d.%d-phb-%d-mmio0",
> - pec->chip_id, pec->index, stack->stack_no);
> + pec->chip_id, pec->index, stack_no);
> memory_region_init(&phb->mmbar0, OBJECT(phb), name, size);
> memory_region_add_subregion(sysmem, bar, &phb->mmbar0);
> phb->mmio0_base = bar;
> @@ -949,7 +971,7 @@ static void pnv_pec_stk_update_map(PnvPHB4 *phb)
> mask = phb->nest_regs[PEC_NEST_STK_MMIO_BAR1_MASK];
> size = ((~mask) >> 8) + 1;
> snprintf(name, sizeof(name), "pec-%d.%d-phb-%d-mmio1",
> - pec->chip_id, pec->index, stack->stack_no);
> + pec->chip_id, pec->index, stack_no);
> memory_region_init(&phb->mmbar1, OBJECT(phb), name, size);
> memory_region_add_subregion(sysmem, bar, &phb->mmbar1);
> phb->mmio1_base = bar;
> @@ -960,7 +982,7 @@ static void pnv_pec_stk_update_map(PnvPHB4 *phb)
> bar = phb->nest_regs[PEC_NEST_STK_PHB_REGS_BAR] >> 8;
> size = PNV_PHB4_NUM_REGS << 3;
> snprintf(name, sizeof(name), "pec-%d.%d-phb-%d",
> - pec->chip_id, pec->index, stack->stack_no);
> + pec->chip_id, pec->index, stack_no);
> memory_region_init(&phb->phbbar, OBJECT(phb), name, size);
> memory_region_add_subregion(sysmem, bar, &phb->phbbar);
> }
> @@ -969,7 +991,7 @@ static void pnv_pec_stk_update_map(PnvPHB4 *phb)
> bar = phb->nest_regs[PEC_NEST_STK_INT_BAR] >> 8;
> size = PNV_PHB4_MAX_INTs << 16;
> snprintf(name, sizeof(name), "pec-%d.%d-phb-%d-int",
> - phb->pec->chip_id, phb->pec->index, stack->stack_no);
> + phb->pec->chip_id, phb->pec->index, stack_no);
> memory_region_init(&phb->intbar, OBJECT(phb), name, size);
> memory_region_add_subregion(sysmem, bar, &phb->intbar);
> }
> @@ -1458,9 +1480,9 @@ static AddressSpace *pnv_phb4_dma_iommu(PCIBus *bus, void *opaque, int devfn)
>
> static void pnv_phb4_xscom_realize(PnvPHB4 *phb)
> {
> - PnvPhb4PecStack *stack = phb->stack;
> PnvPhb4PecState *pec = phb->pec;
> PnvPhb4PecClass *pecc = PNV_PHB4_PEC_GET_CLASS(pec);
> + int stack_no = pnv_phb4_get_phb_stack_no(phb);
> uint32_t pec_nest_base;
> uint32_t pec_pci_base;
> char name[64];
> @@ -1469,20 +1491,20 @@ static void pnv_phb4_xscom_realize(PnvPHB4 *phb)
>
> /* Initialize the XSCOM regions for the stack registers */
> snprintf(name, sizeof(name), "xscom-pec-%d.%d-nest-phb-%d",
> - pec->chip_id, pec->index, stack->stack_no);
> + pec->chip_id, pec->index, stack_no);
> pnv_xscom_region_init(&phb->nest_regs_mr, OBJECT(phb),
> &pnv_pec_stk_nest_xscom_ops, phb, name,
> PHB4_PEC_NEST_STK_REGS_COUNT);
>
> snprintf(name, sizeof(name), "xscom-pec-%d.%d-pci-phb-%d",
> - pec->chip_id, pec->index, stack->stack_no);
> + pec->chip_id, pec->index, stack_no);
> pnv_xscom_region_init(&phb->pci_regs_mr, OBJECT(phb),
> &pnv_pec_stk_pci_xscom_ops, phb, name,
> PHB4_PEC_PCI_STK_REGS_COUNT);
>
> /* PHB pass-through */
> snprintf(name, sizeof(name), "xscom-pec-%d.%d-pci-phb-%d",
> - pec->chip_id, pec->index, stack->stack_no);
> + pec->chip_id, pec->index, stack_no);
> pnv_xscom_region_init(&phb->phb_regs_mr, OBJECT(phb),
> &pnv_phb4_xscom_ops, phb, name, 0x40);
>
> @@ -1491,14 +1513,14 @@ static void pnv_phb4_xscom_realize(PnvPHB4 *phb)
>
> /* Populate the XSCOM address space. */
> pnv_xscom_add_subregion(pec->chip,
> - pec_nest_base + 0x40 * (stack->stack_no + 1),
> + pec_nest_base + 0x40 * (stack_no + 1),
> &phb->nest_regs_mr);
> pnv_xscom_add_subregion(pec->chip,
> - pec_pci_base + 0x40 * (stack->stack_no + 1),
> + pec_pci_base + 0x40 * (stack_no + 1),
> &phb->pci_regs_mr);
> pnv_xscom_add_subregion(pec->chip,
> pec_pci_base + PNV9_XSCOM_PEC_PCI_STK0 +
> - 0x40 * stack->stack_no,
> + 0x40 * stack_no,
> &phb->phb_regs_mr);
> }
>
>
next prev parent reply other threads:[~2022-01-17 10:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 18:07 [PATCH v2 0/8] remove PnvPhb4PecStack from Powernv9 Daniel Henrique Barboza
2022-01-14 18:07 ` [PATCH v2 1/8] ppc/pnv: introduce PnvPHB4 'pec' property Daniel Henrique Barboza
2022-01-14 18:07 ` [PATCH v2 2/8] ppc/pnv: reduce stack->stack_no usage Daniel Henrique Barboza
2022-01-17 10:52 ` Cédric Le Goater [this message]
2022-01-14 18:07 ` [PATCH v2 3/8] ppc/pnv: remove stack pointer from PnvPHB4 Daniel Henrique Barboza
2022-01-14 18:07 ` [PATCH v2 4/8] ppc/pnv: move default_phb_realize() to pec_realize() Daniel Henrique Barboza
2022-01-14 18:07 ` [PATCH v2 5/8] ppc/pnv: remove PnvPhb4PecStack::stack_no Daniel Henrique Barboza
2022-01-17 10:53 ` Cédric Le Goater
2022-01-14 18:07 ` [PATCH v2 6/8] ppc/pnv: make PECs create and realize PHB4s Daniel Henrique Barboza
2022-01-17 10:55 ` Cédric Le Goater
2022-01-14 18:07 ` [PATCH v2 7/8] ppc/pnv: remove PnvPhb4PecStack object Daniel Henrique Barboza
2022-01-14 18:07 ` [PATCH v2 8/8] ppc/pnv: rename pnv_pec_stk_update_map() Daniel Henrique Barboza
2022-01-18 12:03 ` [PATCH v2 0/8] remove PnvPhb4PecStack from Powernv9 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=0f40f8a3-b27b-89d2-b52b-a64fe2705dbf@kaod.org \
--to=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--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).