From: David Hildenbrand <david@redhat.com>
To: qemu-devel@nongnu.org
Cc: David Gibson <david@gibson.dropbear.id.au>,
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v1] spapr/pci: Fix primary bus number for PCI bridges
Date: Wed, 23 Jan 2019 15:23:26 +0100 [thread overview]
Message-ID: <d799bc1c-3d68-ae51-e43c-8ef4ea2b02cc@redhat.com> (raw)
In-Reply-To: <20190123082425.10643-1-david@redhat.com>
On 23.01.19 09: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.
>
> [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.
This note can be dropped. I learned that this is under guest control.
(which has to reserve bus numbers and rebuild the topology)
>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
> 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);
>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-01-23 14: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 [this message]
2019-01-24 2:48 ` Alexey Kardashevskiy
2019-01-25 9:28 ` David Hildenbrand
2019-01-26 1:42 ` David Gibson
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=d799bc1c-3d68-ae51-e43c-8ef4ea2b02cc@redhat.com \
--to=david@redhat.com \
--cc=david@gibson.dropbear.id.au \
--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).