Hi, > That said, Chrome OS would use a similar model, except that we don't > use ION. We would likely use minigbm backed by virtio-gpu to allocate > appropriate secure buffers for us and then import them to the V4L2 > driver. What exactly is a "secure buffer"? I guess a gem object where read access is not allowed, only scanout to display? Who enforces this? The hardware? Or the kernel driver? It might make sense for virtio-gpu to know that concept, to allow guests ask for secure buffers. And of course we'll need some way to pass around identifiers for these (and maybe other) buffers (from virtio-gpu device via guest drivers to virtio-vdec device). virtio-gpu guest driver could generate a uuid for that, attach it to the dma-buf and also notify the host so qemu can maintain a uuid -> buffer lookup table. cheers, Gerd
