RE: [Xen-devel] [PATCH 0/2] IOMMU: Handle sibling device assignmentcorrectly (re-send)

["Ian Pratt" <Ian.Pratt@xxxxxxxxxxxxx>]

> This patch set is revised according to comments from community. Domctl
> interface is extended to allow libxc retrieve device group information
> from hypervisor. Vendor-specific iommu_ops is also extended by adding a
> new operation "get_device_group_id()", which is currently a null
> pointer
> but could be implemented later for vt-d.
> 
> Error will be raised from tools side when user trying to assign PCI
> device with a sibling device being driven by dom0. User will keep being
> prompted until he has hidden the entire device group (at least, the
> sibling devices driven by dom0) in dom0 kernel parameter. Hopefully
> this
> framework could be flexible enough to support both amd iommu and vt-d.
> 
> The following 2 cases are not covered by this patch, but should be easy
> to handle.
> * Checking for hot-plug devices (maybe we can delay calling
> ImageHandler.signalDeviceModel() until all checks are done?)
> * Checking for splitted device group between different passthru domains

With this patch, what happens if you assign a device that is behind a bridge. 
Does the guest get all the devices behind the bridge?

This would be reasonable behaviour, particularly if we prevent other VMs from 
claiming the sibling devices.

Ian

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