From: David Gibson <david@gibson.dropbear.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: David Hildenbrand <david@redhat.com>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v1] spapr/pci: Fix primary bus number for PCI bridges
Date: Sat, 26 Jan 2019 14:42:24 +1300 [thread overview]
Message-ID: <20190126014223.GA22942@umbus> (raw)
In-Reply-To: <11e508cf-bff8-71e0-8d25-b54250d3d201@ozlabs.ru>
[-- Attachment #1: Type: text/plain, Size: 3185 bytes --]
On Thu, Jan 24, 2019 at 01:48:36PM +1100, Alexey Kardashevskiy wrote:
>
>
> On 23/01/2019 19:24, David Hildenbrand wrote:
> > While looking at the s390x implementation, looks like spapr has a
> > similar BUG when building the topology.
> >
> > The primary bus number corresponds always to the bus number of the
> > bus the bridge is attached to.
> >
> > Right now, if we have two bridges attached to the same bus (e.g. root
> > bus) this is however not the case. The first bridge will have primary
> > bus 0, the second bridge primary bus 1, which is wrong. Fix the assignment.
> >
> > While at it, drop setting the PCI_SUBORDINATE_BUS temporarily to 0xff.
> > Setting it temporarily to that value (as discussed e.g. in [1]), is
> > only relevant for a running system that probes the buses. The value is
> > effectively unused for us just doing a DFS.
>
> What is DFS?
>
> >
> > [1] http://www.science.unitn.it/~fiorella/guidelinux/tlk/node76.html
> >
> > Note: Is hotplug of bridges supported? I can't find where the topology
> > is fixed up when hotplugging a PCI bridge. (e.g. bus numbers assigned
> > and PCI_SUBORDINATE_BUS of path to the root updated). But maybe we are
> > excluding bridges or this is not necessary for some reason.
> >
> > Signed-off-by: David Hildenbrand <david@redhat.com>
>
>
> Reviewed-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Applied, thanks.
>
>
> > ---
> > hw/ppc/spapr_pci.c | 5 +----
> > 1 file changed, 1 insertion(+), 4 deletions(-)
> >
> > diff --git a/hw/ppc/spapr_pci.c b/hw/ppc/spapr_pci.c
> > index b74f2632ec..5cdc98513d 100644
> > --- a/hw/ppc/spapr_pci.c
> > +++ b/hw/ppc/spapr_pci.c
> > @@ -2030,8 +2030,6 @@ static void spapr_phb_pci_enumerate_bridge(PCIBus *bus, PCIDevice *pdev,
> > void *opaque)
> > {
> > unsigned int *bus_no = opaque;
> > - unsigned int primary = *bus_no;
> > - unsigned int subordinate = 0xff;
> > PCIBus *sec_bus = NULL;
> >
> > if ((pci_default_read_config(pdev, PCI_HEADER_TYPE, 1) !=
> > @@ -2040,7 +2038,7 @@ static void spapr_phb_pci_enumerate_bridge(PCIBus *bus, PCIDevice *pdev,
> > }
> >
> > (*bus_no)++;
> > - pci_default_write_config(pdev, PCI_PRIMARY_BUS, primary, 1);
> > + pci_default_write_config(pdev, PCI_PRIMARY_BUS, pci_dev_bus_num(pdev), 1);
> > pci_default_write_config(pdev, PCI_SECONDARY_BUS, *bus_no, 1);
> > pci_default_write_config(pdev, PCI_SUBORDINATE_BUS, *bus_no, 1);
> >
> > @@ -2049,7 +2047,6 @@ static void spapr_phb_pci_enumerate_bridge(PCIBus *bus, PCIDevice *pdev,
> > return;
> > }
> >
> > - pci_default_write_config(pdev, PCI_SUBORDINATE_BUS, subordinate, 1);
> > pci_for_each_device(sec_bus, pci_bus_num(sec_bus),
> > spapr_phb_pci_enumerate_bridge, bus_no);
> > pci_default_write_config(pdev, PCI_SUBORDINATE_BUS, *bus_no, 1);
> >
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-01-27 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 8:24 [Qemu-devel] [PATCH v1] spapr/pci: Fix primary bus number for PCI bridges David Hildenbrand
2019-01-23 14:23 ` David Hildenbrand
2019-01-24 2:48 ` Alexey Kardashevskiy
2019-01-25 9:28 ` David Hildenbrand
2019-01-26 1:42 ` David Gibson [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=20190126014223.GA22942@umbus \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--cc=david@redhat.com \
--cc=nikunj@linux.vnet.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).