From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Dongwon Kim <dongwon.kim@intel.com>, qemu-devel@nongnu.org
Cc: "Alex Williamson" <alex.williamson@redhat.com>,
"Cédric Le Goater" <clg@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Vivek Kasireddy" <vivek.kasireddy@intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PATCH v3 0/3] ui/console: initialize QemuDmaBuf in ui/console
Date: Thu, 21 Mar 2024 11:06:32 +0100 [thread overview]
Message-ID: <20240321100635.64950-1-philmd@linaro.org> (raw)
Respin of Dongwon v2 split as bisectable changes.
Unfortunately last patch breaks vhost_user_gpu_handle_display.
Should dbus_scanout_texture() use dpy_gl_create_dmabuf()?
Dongwon, you can use it as a base for a v4.
Regards,
Phil.
Dongwon Kim (3):
ui/console: Introduce dpy_gl_dmabuf_get_height/width() helpers
ui/console: Introduce dpy_gl_dmabuf_get_fd() helper
ui/console: Introduce dpy_gl_create_dmabuf() helper
include/hw/vfio/vfio-common.h | 2 +-
include/hw/virtio/virtio-gpu.h | 2 +-
include/ui/console.h | 10 ++++++
hw/display/virtio-gpu-udmabuf.c | 27 +++++++---------
hw/vfio/display.c | 35 ++++++++++++---------
ui/console.c | 55 +++++++++++++++++++++++++++++++++
6 files changed, 98 insertions(+), 33 deletions(-)
--
2.41.0
next reply other threads:[~2024-03-21 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 10:06 Philippe Mathieu-Daudé [this message]
2024-03-21 10:06 ` [PATCH v3 1/3] ui/console: Introduce dpy_gl_dmabuf_get_height/width() helpers Philippe Mathieu-Daudé
2024-03-21 10:06 ` [PATCH v3 2/3] ui/console: Introduce dpy_gl_dmabuf_get_fd() helper Philippe Mathieu-Daudé
2024-03-21 10:06 ` [INCOMPLETE PATCH v3 3/3] ui/console: Introduce dpy_gl_create_dmabuf() helper Philippe Mathieu-Daudé
2024-03-21 23:46 ` Kim, Dongwon
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=20240321100635.64950-1-philmd@linaro.org \
--to=philmd@linaro.org \
--cc=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=dongwon.kim@intel.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vivek.kasireddy@intel.com \
/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).