[v1] vdpa: Check iova range on memory regions ops

[PATCH 0/3] vdpa: Check iova range on memory regions ops

Eugenio Pérez posted 3 patches 4 years, 4 months ago

Diff against v2 v3 v4
Download series mbox

Test checkpatch passed

Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/20211005080131.408506-1-eperezma@redhat.com

There is a newer version of this series

include/hw/virtio/vhost-vdpa.h |  2 +
hw/virtio/vhost-vdpa.c         | 83 +++++++++++++++++++++++++---------
hw/virtio/trace-events         |  1 +
3 files changed, 65 insertions(+), 21 deletions(-)

Expand all Fold all

[PATCH 0/3] vdpa: Check iova range on memory regions ops

Posted by Eugenio Pérez 4 years, 4 months ago

At this moment vdpa will not send memory regions bigger than 1<<63.
However, actual iova range could be way more restrictive than that.

Since we can obtain the range through vdpa ioctl call, just save it
from the beginning of the operation and check against it.

Eugenio Pérez (3):
  vdpa: Skip protected ram IOMMU mappings
  vdpa: Add vhost_vdpa_section_end
  vdpa: Check for iova range at mappings changes

 include/hw/virtio/vhost-vdpa.h |  2 +
 hw/virtio/vhost-vdpa.c         | 83 +++++++++++++++++++++++++---------
 hw/virtio/trace-events         |  1 +
 3 files changed, 65 insertions(+), 21 deletions(-)

-- 
2.27.0