[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>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Fri, 22 Feb 2008 08:01:26 +0000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 22 Feb 2008 08:22:33 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Ach1KR9XXh8TNuEcEdyzHQAWy6hiGQ==
  • Thread-topic: [Xen-devel] [PATCH 0/3][RFC] PV Passthrough PCI Device Hotplug Support

On 22/2/08 02:03, "Yosuke Iwamatsu" <y-iwamatsu@xxxxxxxxxxxxx> wrote:

> I confess that I have never done a real PCI hot-unplug myself, but
> several specs (acpi spec 3.0b 6.3, pcihp spec 1.1) say that a
> recommended hot removal sequence is like:
>    1. the user notifys the OS of the desire to remove a slot
>    2. the OS logicaly removes the device (unload driver, poweroff, etc)
>       and report the user it's ready
>    3. the user removes the slot
> So the reason I added vdev-# and I chose xend->frontend->backend->xend
> cicle is the same; let the guest OS cleanly shutdown the device first
> and then actually remove it. I think it's quite essential.

Okay, and it does look like Linux makes sensible use of the notification.
I've dug into your patches a bit and actually I think they're fine as is. I
don't think there's much can be done that would significantly simplify them.
I can even live with the extra xenbus states! I'll check the patches in


Xen-devel mailing list



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