From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, clg@kaod.org, fbarrat@linux.ibm.com
Subject: Re: [PATCH v3 0/8] pnv-phb related cleanups
Date: Mon, 27 Jun 2022 18:38:42 -0300 [thread overview]
Message-ID: <fe5ba187-7405-3291-6af6-37368dba8c35@gmail.com> (raw)
In-Reply-To: <20220621173436.165912-1-danielhb413@gmail.com>
Queued in gitlab.com/danielhb/qemu/tree/ppc-next after fixing
the
"We're retrieving a PHB reference PHB just to access"
in the commit msg of patch 03.
Thanks,
Daniel
On 6/21/22 14:34, Daniel Henrique Barboza wrote:
> This version present changes in patch 03. We're now setting chassis and
> slot in pnv_phb_attach_root_port(), avoiding all the hassle of having to
> access the PHB object via bus->qbus.parent inside root_port_realize().
>
> changes from v2:
> - patch 03:
> - set chassis and slot outside of root_port_realize()
> - former patch 04 ("use dev instead of pci->qdev in root_port_realize()"):
> - dropped due to changes in patch 03
> - v2 link: https://lists.gnu.org/archive/html/qemu-devel/2022-06/msg03177.html
>
> Daniel Henrique Barboza (8):
> ppc/pnv: move root port attach to pnv_phb4_realize()
> ppc/pnv: attach phb3/phb4 root ports in QOM tree
> ppc/pnv: assign pnv-phb-root-port chassis/slot earlier
> ppc/pnv: make pnv_ics_get() use the chip8->phbs[] array
> ppc/pnv: make pnv_ics_resend() use chip8->phbs[]
> ppc/pnv: make pnv_chip_power8_pic_print_info() use chip8->phbs[]
> ppc/pnv: remove 'INTERFACE_PCIE_DEVICE' from phb3 root bus
> ppc/pnv: remove 'INTERFACE_PCIE_DEVICE' from phb4 root bus
>
> hw/pci-host/pnv_phb3.c | 22 +-------
> hw/pci-host/pnv_phb4.c | 24 ++-------
> hw/pci-host/pnv_phb4_pec.c | 3 --
> hw/ppc/pnv.c | 102 ++++++++++++++++---------------------
> include/hw/ppc/pnv.h | 3 +-
> 5 files changed, 54 insertions(+), 100 deletions(-)
>
prev parent reply other threads:[~2022-06-27 21:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 17:34 [PATCH v3 0/8] pnv-phb related cleanups Daniel Henrique Barboza
2022-06-21 17:34 ` [PATCH v3 1/8] ppc/pnv: move root port attach to pnv_phb4_realize() Daniel Henrique Barboza
2022-06-21 17:34 ` [PATCH v3 2/8] ppc/pnv: attach phb3/phb4 root ports in QOM tree Daniel Henrique Barboza
2022-06-21 17:34 ` [PATCH v3 3/8] ppc/pnv: assign pnv-phb-root-port chassis/slot earlier Daniel Henrique Barboza
2022-06-22 6:20 ` Cédric Le Goater
2022-06-22 10:06 ` Frederic Barrat
2022-06-21 17:34 ` [PATCH v3 4/8] ppc/pnv: make pnv_ics_get() use the chip8->phbs[] array Daniel Henrique Barboza
2022-06-21 17:34 ` [PATCH v3 5/8] ppc/pnv: make pnv_ics_resend() use chip8->phbs[] Daniel Henrique Barboza
2022-06-21 17:34 ` [PATCH v3 6/8] ppc/pnv: make pnv_chip_power8_pic_print_info() " Daniel Henrique Barboza
2022-06-21 17:34 ` [PATCH v3 7/8] ppc/pnv: remove 'INTERFACE_PCIE_DEVICE' from phb3 root bus Daniel Henrique Barboza
2022-06-21 17:34 ` [PATCH v3 8/8] ppc/pnv: remove 'INTERFACE_PCIE_DEVICE' from phb4 " Daniel Henrique Barboza
2022-06-27 21:38 ` Daniel Henrique Barboza [this message]
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=fe5ba187-7405-3291-6af6-37368dba8c35@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--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).