Question on VirGL/virtio-gpu features

[Alex BennÃe <alex.bennee@linaro.org>]

Hi All,

I was having a discussion the other day with an external team looking at
using virtualised graphics for a production platform. They had some
questions about features I couldn't answer due to my imperfect
understanding of all the moving parts. Does anyone know of any work
being done on the following:

Alternate pixel formats
-----------------------

I believe this is related to pixel data being expressed in different
colour spaces. I see that VIRTIO_GPU_CMD_RESOURCE_CREATE_2D has the
notion of different RGB layouts for pixel data. For 3D pixel data is
this something that is ever visible to the virtio layer or is this all
handled from within the OpenGL interface? I see there is a
VIRTIO_GPU_CMD_SET_SCANOUT_BLOB for defining resources that can get
referenced but that is still restricted to the same virtio_gpu_formats.

Overlay planes
--------------

As I understand it these are used for compositing multiple graphics
sources. We currently working on a virtualised virtio-video backend and
at some point we'll want to consider how you might overlay a 3D view
from one VM with a video source from a second VM and either do the
compositing in the host system or potentially a 3rd VM. Is anyone aware
of any work being done in this direction yet?

vsync
-----

The existing virtio-gpu spec doesn't mention vsync at all. My last
experience with active vsync synchronisation was back in the days of the
Atari ST so I'm a little behind on how it works with modern 3D. Is this
something that ever needs to be exposed to the guest or is it preserve
of the host system to ensure newly drawn frames are swapped out at the
right time to avoid tearing? The Khronos pages refer to Swap Interval
being a platform specific extension. Does this mean it needs to be
something specifically handled by VirGL? 

DRM
---

Probably the least interesting problem from an open source point of view
but I guess for media consumers their needs to be a solution for DRM
protected streams to leave a VM and be handled "somewhere" else. Are
there any proposals for exposing DRM via VirtIO that anyone is aware of?

Any pointers gratefully received! Thanks in advance,

-- 
Alex BennÃe