From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Luqmaan Irshad <luirshad@amd.com>, qemu-devel@nongnu.org
Cc: mst@redhat.com, alex.bennee@linaro.org,
odaki@rsg.ci.i.u-tokyo.ac.jp, pierre-eric.pelloux-prayer@amd.com,
luckmaan21@gmail.com
Subject: Re: [PATCH] virtio-gpu: create drm fd based on specified render node path
Date: Mon, 8 Dec 2025 03:49:59 +0300 [thread overview]
Message-ID: <06bd2abd-e554-4ec8-8ffb-256d33af95c0@collabora.com> (raw)
In-Reply-To: <20251205184906.110927-1-luirshad@amd.com>
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: 20251116125641.2255794-1-dmitry.osipenko@collabora.com
>
> Signed-off-by: Luqmaan Irshad <luirshad@amd.com>
> ---
> 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
next prev parent reply other threads:[~2025-12-08 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 18:49 [PATCH] virtio-gpu: create drm fd based on specified render node path Luqmaan Irshad
2025-12-08 0:49 ` Dmitry Osipenko [this message]
2025-12-09 18:57 ` Irshad, Luqmaan
2025-12-10 15:26 ` Dmitry Osipenko
2025-12-11 14:18 ` Akihiko Odaki
2025-12-11 16:30 ` Irshad, Luqmaan
2025-12-12 3:24 ` Akihiko Odaki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=06bd2abd-e554-4ec8-8ffb-256d33af95c0@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=alex.bennee@linaro.org \
--cc=luckmaan21@gmail.com \
--cc=luirshad@amd.com \
--cc=mst@redhat.com \
--cc=odaki@rsg.ci.i.u-tokyo.ac.jp \
--cc=pierre-eric.pelloux-prayer@amd.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).