[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: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Han, Weidong" <weidong.han@xxxxxxxxx>
  • Date: Tue, 16 Oct 2007 10:04:28 +0800
  • Cc: "Kay, Allen M" <allen.m.kay@xxxxxxxxx>
  • Delivery-date: Mon, 15 Oct 2007 19:05:43 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcgPPrZDfEJfzCOtSJyuGbCE3/cnAQAAjKktABVSMsA=
  • Thread-topic: [Xen-devel] [VTD][PATCH] Don't allow assigning the same device twice without release the first assignment

Keir Fraser wrote:
> 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
> 

Yes, adding the check on DOMCTL_assign_device is simple, but I didn't
find a good way to propagate DOMCTL_assign_device failure to user. This
patch adds the check in xend before starting ioemu. In addtion, adding
the check in Xend can prompt user on the screen when the device has
already been assigned. Thanks.

-- Weidong

_______________________________________________
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®.