From: Albert Esteve <aesteve@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, kraxel@redhat.com, stefanha@gmail.com,
marcandre.lureau@gmail.com
Subject: Re: [PATCH 0/3] Virtio dmabuf improvements
Date: Mon, 4 Dec 2023 10:15:26 +0100 [thread overview]
Message-ID: <CADSE00KHRMM3Cuef1wVTgfZ24s5a11LEkb5MS-T6XGv9XQiS_Q@mail.gmail.com> (raw)
In-Reply-To: <20231204034947-mutt-send-email-mst@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]
On Mon, Dec 4, 2023 at 9:50 AM Michael S. Tsirkin <mst@redhat.com> wrote:
> On Thu, Nov 30, 2023 at 04:49:35PM +0100, Albert Esteve wrote:
> >
> >
> >
> > On Tue, Nov 7, 2023 at 10:37 AM Albert Esteve <aesteve@redhat.com>
> wrote:
> >
> > 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 | 14 +++++-----
> > hw/virtio/vhost-user.c | 33 ++++++++++++++++++-----
> > hw/virtio/vhost.c | 5 ++++
> > include/hw/virtio/vhost.h | 6 +++++
> > include/hw/virtio/virtio-dmabuf.h | 33 ++++++++++++-----------
> > tests/unit/test-virtio-dmabuf.c | 44
> +++++++++++++++----------------
> > 6 files changed, 83 insertions(+), 52 deletions(-)
> >
> > --
> > 2.41.0
> >
> >
> >
> > Bump :)
> >
> > @Marc-André Lureau could you please take a look? You suggested the API
> > upgrades, so would be great if you could check if it is what you had in
> mind.
> >
> > Thanks!
>
> All this is post releas material, right?
>
>
Yes, it is.
[-- Attachment #2: Type: text/html, Size: 2339 bytes --]
prev parent reply other threads:[~2023-12-04 9:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 9:37 [PATCH 0/3] Virtio dmabuf improvements Albert Esteve
2023-11-07 9:37 ` [PATCH 1/3] hw/virtio: check owner for removing objects Albert Esteve
2023-12-04 7:54 ` Marc-André Lureau
2023-12-07 9:14 ` Albert Esteve
2023-11-07 9:37 ` [PATCH 2/3] hw/virtio: cleanup shared resources Albert Esteve
2023-12-04 8:00 ` Marc-André Lureau
2023-12-07 9:18 ` Albert Esteve
2023-11-07 9:37 ` [PATCH 3/3] hw/virtio: rename virtio dmabuf API Albert Esteve
2023-11-30 15:49 ` [PATCH 0/3] Virtio dmabuf improvements Albert Esteve
2023-12-04 8:49 ` Michael S. Tsirkin
2023-12-04 9:15 ` 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=CADSE00KHRMM3Cuef1wVTgfZ24s5a11LEkb5MS-T6XGv9XQiS_Q@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).