From: Alex Williamson <alex.williamson@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: yamahata@valinux.co.jp, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] PCI: Bus number from the bridge, not the device
Date: Mon, 08 Nov 2010 07:52:12 -0700 [thread overview]
Message-ID: <1289227932.19902.11.camel@x201> (raw)
In-Reply-To: <20101108112227.GA1075@redhat.com>
On Mon, 2010-11-08 at 13:22 +0200, Michael S. Tsirkin wrote:
> On Mon, Oct 04, 2010 at 03:53:11PM -0600, Alex Williamson wrote:
> > pcibus_dev_print() was erroneously retrieving the device bus
> > number from the secondary bus number offset of the device
> > instead of the bridge above the device. This ends of landing
> > in the 2nd byte of the 3rd BAR for devices, which thankfully
> > is usually zero. pcibus_get_dev_path() copied this code,
> > inheriting the same bug. pcibus_get_dev_path() is used for
> > ramblock naming, so changing it can effect migration. However,
> > I've only seen this byte be non-zero for an assigned device,
> > which can't migrate anyway, so hopefully we won't run into
> > any issues.
> >
> > Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
>
> Good catch. Applied.
> I don't really see why do we put the dev path
> in the bus object: why not let device supply its name?
Because the device name is not unique. This came about from the
discussion about how to create a canonical device path that Gleb and
Markus are again trying to hash out. If we go up to the bus and get the
bus address, we have a VM unique name. Unfortunately, it's difficult to
define what the bus should print in all cases (ISA), but since they
don't do hotplug and typically don't allocate ramblocks, we can mostly
ignore it for this use case.
> And I think this will affect nested bridges. However they are currently
> broken anyway: we really must convert to topological names as bus number
> is guest-assigned - they don't have to be unique, even.
Yes, nested bridges are a problem. How can the seg/bus/devfn not be
unique?
> What does fixing this involve? Just changing pcibus_get_dev_path?
How do you plan to fix it? Don't forget that migration depends on these
names, so some kind of compatibility layer would be required. Thanks,
Alex
> > ---
> >
> > hw/pci.c | 5 ++---
> > 1 files changed, 2 insertions(+), 3 deletions(-)
> >
> > diff --git a/hw/pci.c b/hw/pci.c
> > index 6d0934d..15416dd 100644
> > --- a/hw/pci.c
> > +++ b/hw/pci.c
> > @@ -1940,8 +1940,7 @@ static void pcibus_dev_print(Monitor *mon, DeviceState *dev, int indent)
> >
> > monitor_printf(mon, "%*sclass %s, addr %02x:%02x.%x, "
> > "pci id %04x:%04x (sub %04x:%04x)\n",
> > - indent, "", ctxt,
> > - d->config[PCI_SECONDARY_BUS],
> > + indent, "", ctxt, pci_bus_num(d->bus),
> > PCI_SLOT(d->devfn), PCI_FUNC(d->devfn),
> > pci_get_word(d->config + PCI_VENDOR_ID),
> > pci_get_word(d->config + PCI_DEVICE_ID),
> > @@ -1965,7 +1964,7 @@ static char *pcibus_get_dev_path(DeviceState *dev)
> > char path[16];
> >
> > snprintf(path, sizeof(path), "%04x:%02x:%02x.%x",
> > - pci_find_domain(d->bus), d->config[PCI_SECONDARY_BUS],
> > + pci_find_domain(d->bus), pci_bus_num(d->bus),
> > PCI_SLOT(d->devfn), PCI_FUNC(d->devfn));
> >
> > return strdup(path);
> >
next prev parent reply other threads:[~2010-11-08 14:52 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 21:53 [Qemu-devel] [PATCH] PCI: Bus number from the bridge, not the device Alex Williamson
2010-11-08 11:22 ` [Qemu-devel] " Michael S. Tsirkin
2010-11-08 14:52 ` Alex Williamson [this message]
2010-11-08 16:26 ` Michael S. Tsirkin
2010-11-08 16:36 ` Alex Williamson
2010-11-08 16:48 ` Michael S. Tsirkin
2010-11-08 17:00 ` Gleb Natapov
2010-11-08 17:08 ` Michael S. Tsirkin
2010-11-08 17:27 ` Gleb Natapov
2010-11-09 2:41 ` Isaku Yamahata
2010-11-09 11:53 ` Michael S. Tsirkin
2010-11-19 17:02 ` Markus Armbruster
2010-11-19 20:38 ` Gleb Natapov
2010-11-20 20:17 ` Michael S. Tsirkin
2010-11-21 8:32 ` Gleb Natapov
2010-11-21 9:50 ` Michael S. Tsirkin
2010-11-21 10:19 ` Gleb Natapov
2010-11-21 11:53 ` Michael S. Tsirkin
2010-11-21 12:50 ` Gleb Natapov
2010-11-21 14:48 ` Michael S. Tsirkin
2010-11-21 16:01 ` Gleb Natapov
2010-11-21 16:38 ` Michael S. Tsirkin
2010-11-21 17:28 ` Gleb Natapov
2010-11-21 18:22 ` Michael S. Tsirkin
2010-11-21 19:29 ` Gleb Natapov
2010-11-21 20:39 ` Michael S. Tsirkin
2010-11-22 7:37 ` Gleb Natapov
2010-11-22 8:16 ` Michael S. Tsirkin
2010-11-22 13:04 ` Gleb Natapov
2010-11-22 14:50 ` Michael S. Tsirkin
2010-11-22 14:52 ` Gleb Natapov
2010-11-22 14:56 ` Michael S. Tsirkin
2010-11-22 14:58 ` Gleb Natapov
2010-11-22 16:41 ` Michael S. Tsirkin
2010-11-22 17:01 ` Gleb Natapov
2010-12-13 20:04 ` Alex Williamson
2010-12-14 4:46 ` Michael S. Tsirkin
2010-12-14 4:49 ` Alex Williamson
2010-12-14 4:57 ` Michael S. Tsirkin
2010-12-14 5:04 ` Alex Williamson
2010-12-14 12:26 ` Michael S. Tsirkin
2010-12-14 18:34 ` Alex Williamson
2010-12-15 9:56 ` Michael S. Tsirkin
2010-12-15 15:27 ` Alex Williamson
2010-12-16 7:08 ` Isaku Yamahata
2010-12-16 8:36 ` Michael S. Tsirkin
2010-12-21 10:13 ` Isaku Yamahata
2010-12-21 10:56 ` Michael S. Tsirkin
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=1289227932.19902.11.camel@x201 \
--to=alex.williamson@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@valinux.co.jp \
/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).