From: dongwon.kim@intel.com
To: qemu-devel@nongnu.org
Cc: marcandre.lureau@redhat.com, berrange@redhat.com
Subject: [PATCH v7 0/5] ui/console: Private QemuDmaBuf struct
Date: Thu, 18 Apr 2024 15:05:36 -0700 [thread overview]
Message-ID: <20240418220541.931134-1-dongwon.kim@intel.com> (raw)
From: Dongwon Kim <dongwon.kim@intel.com>
This series introduces privacy enhancements to the QemuDmaBuf struct
and its contained data to bolster security. it accomplishes this by
introducing of helper functions for allocating, deallocating, and
accessing individual fields within the struct and replacing all direct
references to individual fields in the struct with methods using helpers
throughout the codebase.
This change was made based on a suggestion from Marc-André Lureau
<marcandre.lureau@redhat.com>
(Resumitting same patch series with this new cover-leter)
v6: fixed some typos in patch -
ui/console: Introduce dpy_gl_qemu_dmabuf_get_..() helpers)
v7: included minor fix (ui/gtk: Check if fence_fd is equal to or greater than 0)
(Marc-André Lureau <marcandre.lureau@redhat.com>)
migrated all helpers and QemuDmaBuf struct into dmabuf.c and their prototypes
to dmabuf.h for better encapsulation (ui/dmabuf: New dmabuf.c and dmabuf.h..)
(Daniel P. Berrangé <berrange@redhat.com> and
Marc-André Lureau <marcandre.lureau@redhat.com>)
removed 'dpy_gl' from all helpers' names
Defined autoptr clean up function for QemuDmaBuf*
(Daniel P. Berrangé <berrange@redhat.com>)
Minor corrections
Dongwon Kim (5):
ui/gtk: Check if fence_fd is equal to or greater than 0
ui/console: Introduce qemu_dmabuf_get_..() helpers
ui/console: Introduce qemu_dmabuf_set_..() helpers
ui/console: Introduce qemu_dmabuf_new() and free() helpers
ui/dmabuf: New dmabuf.c and dmabuf.h for QemuDmaBuf struct and helpers
include/hw/vfio/vfio-common.h | 2 +-
include/hw/virtio/virtio-gpu.h | 4 +-
include/ui/console.h | 21 +--
include/ui/dmabuf.h | 38 ++++++
hw/display/vhost-user-gpu.c | 32 +++--
hw/display/virtio-gpu-udmabuf.c | 27 ++--
hw/vfio/display.c | 35 ++---
ui/console.c | 5 +-
ui/dbus-console.c | 9 +-
ui/dbus-listener.c | 71 +++++-----
ui/dmabuf.c | 223 ++++++++++++++++++++++++++++++++
ui/egl-headless.c | 23 +++-
ui/egl-helpers.c | 59 +++++----
ui/gtk-egl.c | 52 +++++---
ui/gtk-gl-area.c | 41 ++++--
ui/gtk.c | 12 +-
ui/spice-display.c | 50 ++++---
ui/meson.build | 1 +
18 files changed, 512 insertions(+), 193 deletions(-)
create mode 100644 include/ui/dmabuf.h
create mode 100644 ui/dmabuf.c
--
2.34.1
next reply other threads:[~2024-04-18 22:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 22:05 dongwon.kim [this message]
2024-04-18 22:05 ` [PATCH v7 1/5] ui/gtk: Check if fence_fd is equal to or greater than 0 dongwon.kim
2024-04-18 22:05 ` [PATCH v7 2/5] ui/console: Introduce qemu_dmabuf_get_..() helpers dongwon.kim
2024-04-18 22:05 ` [PATCH v7 3/5] ui/console: Introduce qemu_dmabuf_set_..() helpers dongwon.kim
2024-04-18 22:05 ` [PATCH v7 4/5] ui/console: Introduce qemu_dmabuf_new() and free() helpers dongwon.kim
2024-04-18 22:05 ` [PATCH v7 5/5] ui/dmabuf: New dmabuf.c and dmabuf.h for QemuDmaBuf struct and helpers dongwon.kim
2024-04-19 6:52 ` Philippe Mathieu-Daudé
2024-04-19 6:53 ` [PATCH v7 0/5] ui/console: Private QemuDmaBuf struct Philippe Mathieu-Daudé
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=20240418220541.931134-1-dongwon.kim@intel.com \
--to=dongwon.kim@intel.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.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).