From: David Hildenbrand <david@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org,
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH v1] spapr/pci: Fix primary bus number for PCI bridges
Date: Fri, 25 Jan 2019 10:28:24 +0100 [thread overview]
Message-ID: <af5b995d-0db2-e64a-1e7b-de5a8b45b64d@redhat.com> (raw)
In-Reply-To: <11e508cf-bff8-71e0-8d25-b54250d3d201@ozlabs.ru>
On 24.01.19 03:48, 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?
Depth-first search :)
>
>>
>> [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>
>
>
Thanks!
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-01-25 9:40 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 [this message]
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=af5b995d-0db2-e64a-1e7b-de5a8b45b64d@redhat.com \
--to=david@redhat.com \
--cc=aik@ozlabs.ru \
--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).