[RFC PATCH] drm/virtio: Export resource handles via DMA-buf API
kraxel at redhat.com
Fri Sep 13 08:07:07 UTC 2019
> > > To seamlessly enable buffer sharing with drivers using such frameworks,
> > > make the virtio-gpu driver expose the resource handle as the DMA address
> > > of the buffer returned from the DMA-buf mapping operation. Arguably, the
> > > resource handle is a kind of DMA address already, as it is the buffer
> > > identifier that the device needs to access the backing memory, which is
> > > exactly the same role a DMA address provides for native devices.
> First of all, thanks for taking a look at this.
> > No. A scatter list has guest dma addresses, period. Stuffing something
> > else into a scatterlist is asking for trouble, things will go seriously
> > wrong when someone tries to use such a fake scatterlist as real scatterlist.
> What is a "guest dma address"? The definition of a DMA address in the
> Linux DMA API is an address internal to the DMA master address space.
> For virtio, the resource handle namespace may be such an address
No. DMA master address space in virtual machines is pretty much the
same it is on physical machines. So, on x86 without iommu, identical
to (guest) physical address space. You can't re-define it like that.
> However, we could as well introduce a separate DMA address
> space if resource handles are not the right way to refer to the memory
> from other virtio devices.
s/other virtio devices/other devices/
dma-bufs are for buffer sharing between devices, not limited to virtio.
You can't re-define that in some virtio-specific way.
> > Also note that "the DMA address of the buffer" is bonkers in virtio-gpu
> > context. virtio-gpu resources are not required to be physically
> > contigous in memory, so typically you actually need a scatter list to
> > describe them.
> There is no such requirement even on a bare metal system, see any
> system that has an IOMMU, which is typical on ARM/ARM64. The DMA
> address space must be contiguous only from the DMA master point of
Yes, the iommu (if present) could remap your scatterlist that way. You
can't depend on that though.
What is the plan here? Host-side buffer sharing I guess? So you are
looking for some way to pass buffer handles from the guest to the host,
even in case those buffers are not created by your driver but imported
from somewhere else?
More information about the dri-devel