[AMD Official Use Only - AMD Internal Distribution Only] Hello Dmitry,
Thats an interesting idea! I would be curious to look into that further, however my ability to do so may be limited since my contract ends at the end of this week. After my contract ends, I won't have access to a multi-GPU system I can test this on. I may be able to work out some way to borrow the system, but at the moment this is uncertain. If this patch looks good, my suggestion would be to merge this change, and we can look into adding this as a separate patch on top of this if I can get access to a system. Let me know how this sounds 🙂 Sincerely, Luq ________________________________ From: Dmitry Osipenko <[email protected]> Sent: Sunday, December 7, 2025 7:49 PM To: Irshad, Luqmaan <[email protected]>; [email protected] <[email protected]> Cc: [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>; Pelloux-Prayer, Pierre-Eric <[email protected]>; [email protected] <[email protected]> Subject: Re: [PATCH] virtio-gpu: create drm fd based on specified render node path 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. > > 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. -- Best regards, Dmitry
