From: Albert Esteve <aesteve@redhat.com>
To: qemu-devel@nongnu.org
Cc: stefanha@gmail.com, "Michael S. Tsirkin" <mst@redhat.com>,
marcandre.lureau@gmail.com, kraxel@redhat.com
Subject: Re: [PATCH v3 0/3] Virtio dmabuf improvements
Date: Mon, 5 Feb 2024 10:58:29 +0100 [thread overview]
Message-ID: <CADSE00+9aokGPszqqr_EMWuR_KZ_fVR-aQSuW3JDDRrOB-6cHw@mail.gmail.com> (raw)
In-Reply-To: <20240109125614.220293-1-aesteve@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1394 bytes --]
Friendly reminder & bump
Is this series waiting to be picked up, or is there anything left to do?
BR,
Albert
On Tue, Jan 9, 2024 at 1:56 PM Albert Esteve <aesteve@redhat.com> wrote:
> v1: https://www.mail-archive.com/qemu-devel@nongnu.org/msg1005257.html
> v2: https://www.mail-archive.com/qemu-devel@nongnu.org/msg1014615.html
> v2 -> v3
> - Documented the new owner check for shared object removal
> - Updated test function names error in the last patch
>
> 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
>
> docs/interop/vhost-user.rst | 4 +-
> 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 ++++++++++++++++++++++---------
> 6 files changed, 141 insertions(+), 53 deletions(-)
>
> --
> 2.43.0
>
>
[-- Attachment #2: Type: text/html, Size: 2313 bytes --]
prev parent reply other threads:[~2024-02-05 9:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 12:56 [PATCH v3 0/3] Virtio dmabuf improvements Albert Esteve
2024-01-09 12:56 ` [PATCH v3 1/3] hw/virtio: check owner for removing objects Albert Esteve
2024-02-05 12:57 ` Alex Bennée
2024-02-15 9:37 ` Albert Esteve
2024-01-09 12:56 ` [PATCH v3 2/3] hw/virtio: cleanup shared resources Albert Esteve
2024-02-05 23:11 ` Alex Bennée
2024-02-15 9:45 ` Albert Esteve
2024-02-15 11:41 ` Alex Bennée
2024-02-19 10:45 ` Albert Esteve
2024-02-19 12:07 ` Albert Esteve
2024-01-09 12:56 ` [PATCH v3 3/3] hw/virtio: rename virtio dmabuf API Albert Esteve
2024-01-09 21:14 ` Philippe Mathieu-Daudé
2024-02-05 9:58 ` Albert Esteve [this message]
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=CADSE00+9aokGPszqqr_EMWuR_KZ_fVR-aQSuW3JDDRrOB-6cHw@mail.gmail.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).