[PATCH 0/2] IOMMU: Handle sibling device assignment correctly (re-send)

[Wei Wang2 <wei.wang2@amd.com>]

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

Looking forward to your comments, thanks!

Wei

Signed-off-by: Wei Wang <wei.wang2@amd.com>
-- 
AMD Saxony, Dresden, Germany
Operating System Research Center

Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
   Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
   AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
   Dr. Hans-R. Deppe, Thomas McCoy