On 2025/12/08 9:49, Dmitry Osipenko wrote:
Hi,
On 12/5/25 21:49, Luqmaan Irshad wrote:
Added a special callback function called virtio_get_drm_fd to create
a render node based on the path specified by the user via QEMU command
line. This function is called during the virglrenderer callback sequence
where we specify the get_drm_fd function pointer to call back our
new function, allowing us to pass the fd of our created render node.
I guess what you need can be achieved by specifying a render node for
the display. Headless displays (egl-headless and dbus) has the
rendernode property for this. For the other displays, Mesa should choose
an appropriate render node, and it can be overridden with the DRI_PRIME
environment variable:
https://docs.mesa3d.org/envvars.html#envvar-DRI_PRIME
Based-on: [email protected]
Signed-off-by: Luqmaan Irshad <[email protected]>
---
hw/display/virtio-gpu-gl.c | 4 ++++
hw/display/virtio-gpu-virgl.c | 17 ++++++++++++++++-
include/hw/virtio/virtio-gpu.h | 1 +
3 files changed, 21 insertions(+), 1 deletion(-)
Do you think it could be possible and worthwhile to make QEMU's EGL
display to use same GPU as virgl automatically? I.e. we tell QEMU/EGL
which GPU to use and then virgl will use same DRM device that backs EGL.
As far as I understand, it is already ensured that virgl uses the EGL
display QEMU uses, and I think that what you want. Opening a different
render node and passing the node to virglrenderer breaks it.
Regards,
Akihiko Odaki
