[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 0/3][RFC] PV Passthrough PCI Device Hotplug Support

  • To: Yosuke Iwamatsu <y-iwamatsu@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Thu, 21 Feb 2008 11:09:17 +0000
  • Delivery-date: Thu, 21 Feb 2008 03:10:04 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Ach0ejL3ca9WjuBtEdyH3gAX8io7RQ==
  • Thread-topic: [Xen-devel] [PATCH 0/3][RFC] PV Passthrough PCI Device Hotplug Support

On 21/2/08 11:00, "Yosuke Iwamatsu" <y-iwamatsu@xxxxxxxxxxxxx> wrote:

> - Interface changes
>   New xenbus states "Reconfiguring" and "Reconfigured" are introduced.

Not sure about this. If this is just to flag changes to individual devices,
could pcifront watch individual device nodes? Or at least I think a separate
configuration xenstore node would be sensible, with its own state-machine
enumeration. I'm reluctant to mess with the main state node as we currently
have something that works!

> - Xenstore changes
>   Substates(state-#) and virtual pci slots(vdev-#) entries are added
>   for pciback driver. For example, when PCI devices 00:1d.0 and 00:1d.1
>   are connected, xenstore-ls will show information like this.

Why vdev-#? Aren't the dev-# names already the virtual names (mapped to
physical slots transparently by pciback)?

 -- Keir

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.