> Generally we try to cache mappings as much as possible. And wrt finding a
> slot: Create a sufficiently sized BAR on the virgl device, just for that?
Well. virtio has no concept of "bars" ...
The most common virtio transport layer happens to be pci, which actually
has bars. But we also have virtio-mmio (largely unused since arm got
pci) and virtio-ccw (used on s390x).
In any case it would be a layering violation.
Figured meanwhile qemu got memfd support recently, i.e. it can be
configured to back guest memory with memfd. Which makes the memfd route
quite attractive. Guess I try switch udmabuf to require memfd storage
dri-devel mailing list