On 04/30/2013 10:49 AM, Eric Blake wrote:
> On 04/29/2013 07:46 PM, Laine Stump wrote:
+int qemuSetupHostdevCGroup(virDomainObjPtr vm,
+ virDomainHostdevDefPtr dev)
ATTRIBUTE_RETURN_CHECK;
+int qemuTeardownHostdevCgroup(virDomainObjPtr vm,
+
On 04/29/2013 07:46 PM, Laine Stump wrote:
>>> +int qemuSetupHostdevCGroup(virDomainObjPtr vm,
>>> + virDomainHostdevDefPtr dev)
>>> ATTRIBUTE_RETURN_CHECK;
>>> +int qemuTeardownHostdevCgroup(virDomainObjPtr vm,
>>> + virDomainHostdevDefPtr de
On 04/29/2013 05:46 PM, Eric Blake wrote:
> On 04/29/2013 02:28 PM, Laine Stump wrote:
>> PCIO device assignment using VFIO requires read/write access by the
>> qemu process to /dev/vfio/vfio, and /dev/vfio/nn, where "nn" is the
>> VFIO group number that the assigned device belongs to (and can be
>
On 04/29/2013 02:28 PM, Laine Stump wrote:
> PCIO device assignment using VFIO requires read/write access by the
> qemu process to /dev/vfio/vfio, and /dev/vfio/nn, where "nn" is the
> VFIO group number that the assigned device belongs to (and can be
> found with the function virPCIDeviceGetVFIOGro
PCIO device assignment using VFIO requires read/write access by the
qemu process to /dev/vfio/vfio, and /dev/vfio/nn, where "nn" is the
VFIO group number that the assigned device belongs to (and can be
found with the function virPCIDeviceGetVFIOGroupDev)
/dev/vfio/vfio can be accessible to any gue