search for: vdpa_map_fil

...) [Jason] - add unbind_mm callback [Jason] include/linux/vdpa.h | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/include/linux/vdpa.h b/include/linux/vdpa.h index 43f59ef10cc9..369c21394284 100644 --- a/include/linux/vdpa.h +++ b/include/linux/vdpa.h @@ -290,6 +290,14 @@ struct vdpa_map_file { * @vdev: vdpa device * @idx: virtqueue index * Returns pointer to structure device or error (NULL) + * @bind_mm: Bind the device to a specific address space + * so the vDPA framework can use VA when this + * callback is implemented. (optional) + * @vdev: vdpa device + *...

...- name, dma_dev); + notify, callback, name, dma_dev); if (!vq) { err = -ENOMEM; goto error_new_virtqueue; diff --git a/include/linux/vdpa.h b/include/linux/vdpa.h index 43f59ef10cc..a83bb0501c5 100644 --- a/include/linux/vdpa.h +++ b/include/linux/vdpa.h @@ -143,6 +143,11 @@ struct vdpa_map_file { * @kick_vq: Kick the virtqueue * @vdev: vdpa device * @idx: virtqueue index + * @kick_vq_with_data: Kick the virtqueue and supply extra data + * (only if VIRTIO_F_NOTIFICATION_DATA is negotiated) + * @vdev: vdpa device + * @data: includes vqn, next_off and next_wrap for +...

...gt; >> 1 file changed, 7 insertions(+) > >> > >> diff --git a/include/linux/vdpa.h b/include/linux/vdpa.h > >> index db1b0ea..3a3878d 100644 > >> --- a/include/linux/vdpa.h > >> +++ b/include/linux/vdpa.h > >> @@ -314,6 +314,12 @@ struct vdpa_map_file { > >> * @iova: iova to be unmapped > >> * @size: size of the area > >> * Returns integer: success (0) or error (< 0) > >> + * @reset_map: Reset devic...

...PFN_DOWN(notify.addr), PAGE_SIZE, > vma->vm_page_prot)) > diff --git a/include/linux/vdpa.h b/include/linux/vdpa.h > index 6d0f5e4e82c2..07fcf5e6abc8 100644 > --- a/include/linux/vdpa.h > +++ b/include/linux/vdpa.h > @@ -169,6 +169,12 @@ struct vdpa_map_file { > * @vdev: vdpa device > * @idx: virtqueue index > * Returns the notifcation area > + * @get_vq_notification_pgprot: Get the pgprot of the vq's notification area (optional) > + *...

...nvqs; ++i) { > if (!names[i]) { > vqs[i] = NULL; > diff --git a/include/linux/vdpa.h b/include/linux/vdpa.h > index d61f369f9cd6..10bd22387276 100644 > --- a/include/linux/vdpa.h > +++ b/include/linux/vdpa.h > @@ -259,6 +259,13 @@ struct vdpa_map_file { > * @vdev: vdpa device > * @idx: virtqueue index > * Returns the irq affinity mask > + * @set_irq_affinity: Pass the irq affinity hint (best effort) Note that this could easily confuse...

...lback, name, dma_dev); > if (!vq) { > err = -ENOMEM; > goto error_new_virtqueue; > diff --git a/include/linux/vdpa.h b/include/linux/vdpa.h > index 43f59ef10cc..a83bb0501c5 100644 > --- a/include/linux/vdpa.h > +++ b/include/linux/vdpa.h > @@ -143,6 +143,11 @@ struct vdpa_map_file { > * @kick_vq: Kick the virtqueue > * @vdev: vdpa device > * @idx: virtqueue index > + * @kick_vq_with_data: Kick the virtqueue and supply extra data > + * (only if VIRTIO_F_NOTIFICATION_DATA is negotiated) > + * @vdev: vdpa device > + * @data: include...

...if (!vq) { > err = -ENOMEM; > goto error_new_virtqueue; > diff --git a/include/linux/vdpa.h b/include/linux/vdpa.h > index 43f59ef10cc..a83bb0501c5 100644 > --- a/include/linux/vdpa.h > +++ b/include/linux/vdpa.h > @@ -143,6 +143,11 @@ struct vdpa_map_file { > * @kick_vq: Kick the virtqueue > * @vdev: vdpa device > * @idx: virtqueue index > + * @kick_vq_with_data: Kick the virtqueue and supply extra data > + * (only if V...

...- name, dma_dev); + notify, callback, name, dma_dev); if (!vq) { err = -ENOMEM; goto error_new_virtqueue; diff --git a/include/linux/vdpa.h b/include/linux/vdpa.h index 43f59ef10cc..04cdaad77dd 100644 --- a/include/linux/vdpa.h +++ b/include/linux/vdpa.h @@ -143,6 +143,14 @@ struct vdpa_map_file { * @kick_vq: Kick the virtqueue * @vdev: vdpa device * @idx: virtqueue index + * @kick_vq_with_data: Kick the virtqueue and supply extra data + * (only if VIRTIO_F_NOTIFICATION_DATA is negotiated) + * @vdev: vdpa device + * @data for split virtqueue: + * 16 bits vqn and...

...;> >>>>>> diff --git a/include/linux/vdpa.h b/include/linux/vdpa.h >>>>>> index db1b0ea..3a3878d 100644 >>>>>> --- a/include/linux/vdpa.h >>>>>> +++ b/include/linux/vdpa.h >>>>>> @@ -314,6 +314,12 @@ struct vdpa_map_file { >>>>>> * @iova: iova to be unmapped >>>>>> * @size: size of the area >>>>>> * Returns integer: success (0) or error (< 0) >>>>&g...

Following patchset introduces dedicated group for descriptor table to reduce live migration downtime when passthrough VQ is being switched to shadow VQ. This RFC v2 is sent to incorporate the early feedback from reviewers on the uAPI and driver API part of changes, the associated driver patch set consuming ths API will come around soon along with formal submission of this series. Some initial

In order to reduce needlessly high setup and teardown cost of iotlb mapping during live migration, it's crucial to decouple the vhost-vdpa iotlb abstraction from the virtio device life cycle, i.e. iotlb mappings should be left intact across virtio device reset [1]. For it to work, the on-chip IOMMU parent device should implement a separate .reset_map() operation callback to restore 1:1 DMA

In order to reduce needlessly high setup and teardown cost of iotlb mapping during live migration, it's crucial to decouple the vhost-vdpa iotlb abstraction from the virtio device life cycle, i.e. iotlb mappings should be left intact across virtio device reset [1]. For it to work, the on-chip IOMMU parent device should implement a separate .reset_map() operation callback to restore 1:1 DMA

This series adds support for the use of user virtual addresses in the vDPA simulator devices. The main reason for this change is to lift the pinning of all guest memory. Especially with virtio devices implemented in software. The next step would be to generalize the code in vdpa-sim to allow the implementation of in-kernel software devices. Similar to vhost, but using vDPA so we can reuse the

v2: - rebased on Linus' tree, commit ae3419fbac84 ("vc_screen: don't clobber return value in vcs_read") - removed `struct task_struct *owner` param (unused for now, maybe ?useful to support cgroups) [Jason] - add unbind_mm callback [Jason] - call the new unbind_mm callback during the release [Jason] - avoid to call bind_mm callback after the reset, since the device ?is not

This series adds support for the use of user virtual addresses in the vDPA simulator devices. The main reason for this change is to lift the pinning of all guest memory. Especially with virtio devices implemented in software. The next step would be to generalize the code in vdpa-sim to allow the implementation of in-kernel software devices. Similar to vhost, but using vDPA so we can reuse the