qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Isaku Yamahata <yamahata@valinux.co.jp>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	qemu-devel@nongnu.org, gleb@redhat.com
Subject: [Qemu-devel] Re: [PATCH repost] pci: fix migration device path for devices behind nested bridges
Date: Fri, 24 Dec 2010 18:26:42 +0900	[thread overview]
Message-ID: <20101224092642.GH7603@valinux.co.jp> (raw)
In-Reply-To: <20101224084529.GA23180@redhat.com>

The code looks good.
Regarding to the format itself, I don't have strong opinion about it.

What cames into my mind while I'm looking at the code is,
Does BusInfo have to have two path functions? get_dev_path and get_fw_dev_path.
Right now only pci supplies get_dev_path, on the other hand
get_fw_dev_path covers more buses.
This would be another topic, though.

On Fri, Dec 24, 2010 at 10:45:29AM +0200, Michael S. Tsirkin wrote:
> We were using bus number in the device path, which is clearly
> broken as this number is guest-assigned for all devices
> except the root.
> 
> Replace this by a hierarchical list of slot/function numbers, walking
> the path from root down to device. Add :00 after the domain number
> so that if there are no nested bridges, this is compatible
> with what we have now.
> 
> Note: as pointed out by Gleb, using openfirmware paths
> might be cleaner, doing this would break compatibility though,
> and the IDs used are not guest or user visible at all,
> so it probably doesn't matter what they are exactly.
> 
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> 
> OK I think I'll just apply the below, it seems better for the
> next release than the alternative of disabling migration
> completely, and the IDs used are completely transparent to
> the user, so it probably doesn't matter what they are exactly.
> 
>  hw/pci.c |   44 ++++++++++++++++++++++++++++++++++++--------
>  1 files changed, 36 insertions(+), 8 deletions(-)
> 
> diff --git a/hw/pci.c b/hw/pci.c
> index 8f6fcf8..aed2d42 100644
> --- a/hw/pci.c
> +++ b/hw/pci.c
> @@ -1826,15 +1826,41 @@ static void pcibus_dev_print(Monitor *mon, DeviceState *dev, int indent)
>  
>  static char *pcibus_get_dev_path(DeviceState *dev)
>  {
> -    PCIDevice *d = (PCIDevice *)dev;
> -    char path[16];
> -
> -    snprintf(path, sizeof(path), "%04x:%02x:%02x.%x",
> -             pci_find_domain(d->bus),
> -             0 /* TODO: need a persistent path for nested buses.
> -                * Note: pci_bus_num(d->bus) is not right as it's guest
> -                * assigned. */,
> -             PCI_SLOT(d->devfn), PCI_FUNC(d->devfn));
> -
> -    return strdup(path);
> +    PCIDevice *d = container_of(dev, PCIDevice, qdev);
> +    PCIDevice *t;
> +    int slot_depth;
> +    /* Path format: Domain:00:Slot.Function:Slot.Function....:Slot.Function.
> +     * 00 is added here to make this format compatible with
> +     * domain:Bus:Slot.Func for systems without nested PCI bridges.
> +     * Slot.Function list specifies the slot and function numbers for all
> +     * devices on the path from root to the specific device. */
> +    int domain_len = strlen("DDDD:00");
> +    int slot_len = strlen(":SS.F");
> +    int path_len;
> +    char *path, *p;
> +
> +    /* Calculate # of slots on path between device and root. */;
> +    slot_depth = 0;
> +    for (t = d; t; t = t->bus->parent_dev)
> +        ++slot_depth;
> +
> +    path_len = domain_len + slot_len * slot_depth;
> +
> +    /* Allocate memory, fill in the terminating null byte. */
> +    path = malloc(path_len + 1 /* For '\0' */);
> +    path[path_len] = '\0';
> +
> +    /* First field is the domain. */
> +    snprintf(path, domain_len, "%04x:00", pci_find_domain(d->bus));
> +
> +    /* Fill in slot numbers. We walk up from device to root, so need to print
> +     * them in the reverse order, last to first. */
> +    p = path + path_len;
> +    for (t = d; t; t = t->bus->parent_dev) {
> +        p -= slot_len;
> +        snprintf(p, slot_len, ":%02x.%x", PCI_SLOT(t->devfn), PCI_FUNC(d->devfn));
> +    }
> +
> +    return path;
>  }
>  
> -- 
> 1.7.3.2.91.g446ac
> 

-- 
yamahata

  reply	other threads:[~2010-12-24  9:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-24  8:45 [Qemu-devel] [PATCH repost] pci: fix migration device path for devices behind nested bridges Michael S. Tsirkin
2010-12-24  9:26 ` Isaku Yamahata [this message]
2010-12-24 12:37   ` [Qemu-devel] " 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=20101224092642.GH7603@valinux.co.jp \
    --to=yamahata@valinux.co.jp \
    --cc=alex.williamson@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=gleb@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@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).