Hi Gerd, On Thu, Sep 12, 2019 at 9:38 PM Gerd Hoffmann <kraxel@xxxxxxxxxx> wrote: > > Hi, > > > 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 space. 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. > > 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 view. Best regards, Tomasz _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
