From: Albert Esteve <aesteve@redhat.com>
To: qemu-devel@nongnu.org
Cc: marcandre.lureau@gmail.com, kraxel@redhat.com,
"Michael S. Tsirkin" <mst@redhat.com>,
stefanha@gmail.com, Albert Esteve <aesteve@redhat.com>
Subject: [PATCH v2 0/3] Virtio dmabuf improvements
Date: Thu, 7 Dec 2023 15:55:42 +0100 [thread overview]
Message-ID: <20231207145545.783877-1-aesteve@redhat.com> (raw)
v1: https://www.mail-archive.com/qemu-devel@nongnu.org/msg1005257.html
v1 -> v2:
- Solved an unitialized uuid value on vhost-user source
- Changed cleanup strategy, and traverse all objects in the
table to remove them instead.
Various improvements for the virtio-dmabuf module.
This patch includes:
- Check for ownership before allowing a vhost device
to remove an object from the table.
- Properly cleanup shared resources if a vhost device
object gets cleaned up.
- Rename virtio dmabuf functions to `virtio_dmabuf_*`
Albert Esteve (3):
hw/virtio: check owner for removing objects
hw/virtio: cleanup shared resources
hw/virtio: rename virtio dmabuf API
hw/display/virtio-dmabuf.c | 36 ++++++++++++---
hw/virtio/vhost-user.c | 31 ++++++++++---
hw/virtio/vhost.c | 3 ++
include/hw/virtio/virtio-dmabuf.h | 43 ++++++++++-------
tests/unit/test-virtio-dmabuf.c | 77 ++++++++++++++++++++++---------
5 files changed, 138 insertions(+), 52 deletions(-)
--
2.43.0
next reply other threads:[~2023-12-07 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 14:55 Albert Esteve [this message]
2023-12-07 14:55 ` [PATCH v2 1/3] hw/virtio: check owner for removing objects Albert Esteve
2023-12-07 14:55 ` [PATCH v2 2/3] hw/virtio: cleanup shared resources Albert Esteve
2023-12-07 14:55 ` [PATCH v2 3/3] hw/virtio: rename virtio dmabuf API Albert Esteve
2023-12-07 15:30 ` Albert Esteve
2023-12-11 21:47 ` [PATCH v2 0/3] Virtio dmabuf improvements Stefan Hajnoczi
2024-01-08 15:48 ` Albert Esteve
2024-01-08 15:56 ` Stefan Hajnoczi
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=20231207145545.783877-1-aesteve@redhat.com \
--to=aesteve@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).