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

Re: [Xen-devel] [VTD][PATCH] Don't allow assigning the same device twice without release the first assignment


  • To: "Han, Weidong" <weidong.han@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Mon, 15 Oct 2007 16:34:44 +0100
  • Cc: "Kay, Allen M" <allen.m.kay@xxxxxxxxx>
  • Delivery-date: Mon, 15 Oct 2007 08:35:33 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcgPPrZDfEJfzCOtSJyuGbCE3/cnAQAAjKkt
  • Thread-topic: [Xen-devel] [VTD][PATCH] Don't allow assigning the same device twice without release the first assignment

The DOMCTL_assign_device should check whether the device is already
assigned. This has the benefit that it can atomically check-and-allocate,
under the domctl lock.

You'll have to work out how to propagate DOMCTL_assign_device failure to the
user. Either you have to get the error out of ioemu, or perhaps you can
assign the device in xend before starting ioemu.

 -- Keir

On 15/10/07 16:19, "Han, Weidong" <weidong.han@xxxxxxxxx> wrote:

> System will hang, if assign the same device to domains twice without
> release the first assignment. This patch checks whether the device
> already has been assigned or not before creating domain, if yes, display
> prompt message and won't create the domain.
> 
> Signed-off-by: Weidong Han <weidong.han@xxxxxxxxx>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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