vdpa_sim: use iova module to allocate IOVA addresses

Browse source

The identical mapping used until now created issues when mapping
different virtual pages with the same physical address.
To solve this issue, we can use the iova module, to handle the IOVA
allocation.
For simplicity we use an IOVA allocator with byte granularity.

We add two new functions, vdpasim_map_range() and vdpasim_unmap_range(),
to handle the IOVA allocation and the registration into the IOMMU/IOTLB.
These functions are used by dma_map_ops callbacks.

Acked-by: Jason Wang <jasowang@redhat.com>
Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
Link: https://lore.kernel.org/r/20210315163450.254396-2-sgarzare@redhat.com
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

...

This commit is contained in:

Stefano Garzarella 2021-03-15 17:34:37 +01:00 • committed by Michael S. Tsirkin

parent e8ef612495

commit 4080fc1067

3 changed files with 69 additions and 42 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

1

drivers/vdpa/Kconfig

View file

108

drivers/vdpa/vdpa_sim/vdpa_sim.c

View file

2

drivers/vdpa/vdpa_sim/vdpa_sim.h

View file