On Wed, Jun 17, 2020 at 11:29:46AM +0800, Jason Wang wrote:
In order to let userspace work correctly, get_iova_range() is a mustI guess you mean for a device.
for the device that has its own DMA translation logic.
However in absence of ths op, I don't see what is wrong with just
assuming device can access any address.
Signed-off-by: Jason Wang <jasowang@xxxxxxxxxx>What about devices using an IOMMU for translation?
drivers/vdpa/vdpa.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/vdpa/vdpa.c b/drivers/vdpa/vdpa.c
index de211ef3738c..ab7af978ef70 100644
@@ -82,6 +82,10 @@ struct vdpa_device *__vdpa_alloc_device(struct device *parent,
if (!!config->dma_map != !!config->dma_unmap)
+ if ((config->dma_map || config->set_map) &&
+ goto err;
err = -ENOMEM;
vdev = kzalloc(size, GFP_KERNEL);
IOMMUs generally have a limited IOVA range too, right?