search for: vfio_vhost_vq_irq_index

Displaying 9 results from an estimated 9 matches for "vfio_vhost_vq_irq_index".

2019 Jul 03
4
[RFC v2] vhost: introduce mdev based hardware vhost backend
...= pwrite64(vfio->device_fd, &queue_idx, sizeof(queue_idx), vfio->notify_offset + offset); ...... } 3. VFIO interrupt ioctl API VFIO interrupt ioctl API is used to setup device interrupts. IRQ-bypass can also be supported. Currently, the data path interrupt can be configured via the VFIO_VHOST_VQ_IRQ_INDEX with virtqueue's callfd. Signed-off-by: Tiwei Bie <tiwei.bie at intel.com> --- drivers/vhost/Makefile | 2 + drivers/vhost/vdpa.c | 770 +++++++++++++++++++++++++++++++++++++ include/linux/vdpa_mdev.h | 72 ++++ include/uapi/linux/vfio.h | 19 + include/uapi/linux/vhost....
2019 Jul 03
4
[RFC v2] vhost: introduce mdev based hardware vhost backend
...= pwrite64(vfio->device_fd, &queue_idx, sizeof(queue_idx), vfio->notify_offset + offset); ...... } 3. VFIO interrupt ioctl API VFIO interrupt ioctl API is used to setup device interrupts. IRQ-bypass can also be supported. Currently, the data path interrupt can be configured via the VFIO_VHOST_VQ_IRQ_INDEX with virtqueue's callfd. Signed-off-by: Tiwei Bie <tiwei.bie at intel.com> --- drivers/vhost/Makefile | 2 + drivers/vhost/vdpa.c | 770 +++++++++++++++++++++++++++++++++++++ include/linux/vdpa_mdev.h | 72 ++++ include/uapi/linux/vfio.h | 19 + include/uapi/linux/vhost....
2019 Jul 03
2
[RFC v2] vhost: introduce mdev based hardware vhost backend
...+1 > > > > [...] > > > > 3. VFIO interrupt ioctl API > > > > VFIO interrupt ioctl API is used to setup device interrupts. > > IRQ-bypass can also be supported. > > > > Currently, the data path interrupt can be configured via the > > VFIO_VHOST_VQ_IRQ_INDEX with virtqueue's callfd. > > > How about DMA API? Do you expect to use VFIO IOMMU API or using vhost > SET_MEM_TABLE? VFIO IOMMU API is more generic for sure but with > SET_MEM_TABLE DMA can be done at the level of parent device which means it > can work for e.g the card wit...
2019 Jul 03
2
[RFC v2] vhost: introduce mdev based hardware vhost backend
...+1 > > > > [...] > > > > 3. VFIO interrupt ioctl API > > > > VFIO interrupt ioctl API is used to setup device interrupts. > > IRQ-bypass can also be supported. > > > > Currently, the data path interrupt can be configured via the > > VFIO_VHOST_VQ_IRQ_INDEX with virtqueue's callfd. > > > How about DMA API? Do you expect to use VFIO IOMMU API or using vhost > SET_MEM_TABLE? VFIO IOMMU API is more generic for sure but with > SET_MEM_TABLE DMA can be done at the level of parent device which means it > can work for e.g the card wit...
2019 Jul 03
0
[RFC v2] vhost: introduce mdev based hardware vhost backend
...f(queue_idx), > vfio->notify_offset + offset); > ...... > } > > 3. VFIO interrupt ioctl API > > VFIO interrupt ioctl API is used to setup device interrupts. > IRQ-bypass can also be supported. > > Currently, the data path interrupt can be configured via the > VFIO_VHOST_VQ_IRQ_INDEX with virtqueue's callfd. How about DMA API? Do you expect to use VFIO IOMMU API or using vhost SET_MEM_TABLE? VFIO IOMMU API is more generic for sure but with SET_MEM_TABLE DMA can be done at the level of parent device which means it can work for e.g the card with on-chip IOMMU. And what&...
2019 Jul 03
0
[RFC v2] vhost: introduce mdev based hardware vhost backend
...+ * IRQ index mapping. Unimplemented regions return a size of zero. > + * Unimplemented IRQ types return a count of zero. > + */ > + > +enum { > + VFIO_VHOST_CONFIG_REGION_INDEX, > + VFIO_VHOST_NOTIFY_REGION_INDEX, > + VFIO_VHOST_NUM_REGIONS > +}; > + > +enum { > + VFIO_VHOST_VQ_IRQ_INDEX, > + VFIO_VHOST_NUM_IRQS > +}; > + Note that the vfio API has evolved a bit since vfio-pci started this way, with fixed indexes for pre-defined region types. We now support device specific regions which can be identified by a capability within the REGION_INFO ioctl return data. This all...
2019 Jul 03
0
[RFC v2] vhost: introduce mdev based hardware vhost backend
...> >> > [...] >>> 3. VFIO interrupt ioctl API >>> >>> VFIO interrupt ioctl API is used to setup device interrupts. >>> IRQ-bypass can also be supported. >>> >>> Currently, the data path interrupt can be configured via the >>> VFIO_VHOST_VQ_IRQ_INDEX with virtqueue's callfd. >> >> How about DMA API? Do you expect to use VFIO IOMMU API or using vhost >> SET_MEM_TABLE? VFIO IOMMU API is more generic for sure but with >> SET_MEM_TABLE DMA can be done at the level of parent device which means it >> can work for e.g...
2019 Jul 03
2
[RFC v2] vhost: introduce mdev based hardware vhost backend
...O interrupt ioctl API > > > > > > > > VFIO interrupt ioctl API is used to setup device interrupts. > > > > IRQ-bypass can also be supported. > > > > > > > > Currently, the data path interrupt can be configured via the > > > > VFIO_VHOST_VQ_IRQ_INDEX with virtqueue's callfd. > > > > > > How about DMA API? Do you expect to use VFIO IOMMU API or using vhost > > > SET_MEM_TABLE? VFIO IOMMU API is more generic for sure but with > > > SET_MEM_TABLE DMA can be done at the level of parent device which means it...
2019 Jul 03
2
[RFC v2] vhost: introduce mdev based hardware vhost backend
...O interrupt ioctl API > > > > > > > > VFIO interrupt ioctl API is used to setup device interrupts. > > > > IRQ-bypass can also be supported. > > > > > > > > Currently, the data path interrupt can be configured via the > > > > VFIO_VHOST_VQ_IRQ_INDEX with virtqueue's callfd. > > > > > > How about DMA API? Do you expect to use VFIO IOMMU API or using vhost > > > SET_MEM_TABLE? VFIO IOMMU API is more generic for sure but with > > > SET_MEM_TABLE DMA can be done at the level of parent device which means it...