On 19/03/18 09:47, Yisheng Xie wrote:
> Hi Jean,
>
> vfio can be compiled as module, however you use some functions which are not
> exported.
Oh right. I remember the kbuild test robot warning about this once, I
wonder why it didn't find this one.
> comment inline:
>
> [...]
>> Add two new
Hi Jean,
vfio can be compiled as module, however you use some functions which are not
exported.
comment inline:
[...]
> Add two new ioctl for VFIO containers. VFIO_IOMMU_BIND_PROCESS creates a
> bond between a container and a process address space, identified by a
> device-specific ID named
On 28/02/18 01:26, Sinan Kaya wrote:
[...]
>> +static int vfio_iommu_sva_init(struct device *dev, void *data)
>> +{
>
> data is not getting used.
That's the pointer passed to "iommu_group_for_each_dev", NULL at the
moment. Next version of this patch will keep some state in data to
ensure one
On 2/12/2018 1:33 PM, Jean-Philippe Brucker wrote:
> Add two new ioctl for VFIO containers. VFIO_IOMMU_BIND_PROCESS creates a
> bond between a container and a process address space, identified by a
> device-specific ID named PASID. This allows the device to target DMA
> transactions at the process
On 16/02/18 19:33, Alex Williamson wrote:
[...]
>> +static int vfio_iommu_sva_init(struct device *dev, void *data)
>> +{
>> +
>> +int ret;
>> +
>> +ret = iommu_sva_device_init(dev, IOMMU_SVA_FEAT_PASID |
>> +IOMMU_SVA_FEAT_IOPF, 0);
>> +if (ret)
>> +
On Mon, 12 Feb 2018 18:33:52 +
Jean-Philippe Brucker wrote:
> Add two new ioctl for VFIO containers. VFIO_IOMMU_BIND_PROCESS creates a
> bond between a container and a process address space, identified by a
> device-specific ID named PASID. This allows the
Add two new ioctl for VFIO containers. VFIO_IOMMU_BIND_PROCESS creates a
bond between a container and a process address space, identified by a
device-specific ID named PASID. This allows the device to target DMA
transactions at the process virtual addresses without a need for mapping
and unmapping