qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Albert Esteve <aesteve@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@gmail.com,
	alex.bennee@linaro.org, philmd@linaro.org, kraxel@redhat.com,
	marcandre.lureau@gmail.com
Subject: Re: [PATCH v4 0/5] Virtio dmabuf improvements
Date: Tue, 12 Mar 2024 14:23:26 -0400	[thread overview]
Message-ID: <20240312142033-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240219143423.272012-1-aesteve@redhat.com>

On Mon, Feb 19, 2024 at 03:34:18PM +0100, Albert Esteve 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
> v3: Virtio dmabuf improvements
> v3 -> v4
>   - Changed GMutex by QemuMutex in virtio-dmabuf
>   - Made the value at VirtioSharedObject an union
>     to make naming more clear
>   - Added some documentation

Dropped everything except patch 1 for now.

> 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 (5):
>   hw/virtio: check owner for removing objects
>   hw/virtio: document SharedObject structures
>   hw/virtio: change dmabuf mutex to QemuMutex
>   hw/virtio: cleanup shared resources
>   hw/virtio: rename virtio dmabuf API
> 
>  docs/interop/vhost-user.rst       |  4 +-
>  hw/display/virtio-dmabuf.c        | 98 +++++++++++++++++++------------
>  hw/virtio/vhost-user.c            | 31 +++++++---
>  hw/virtio/vhost.c                 |  3 +
>  hw/virtio/virtio.c                |  3 +
>  include/hw/virtio/virtio-dmabuf.h | 73 +++++++++++++++++------
>  tests/unit/test-virtio-dmabuf.c   | 82 +++++++++++++++++++-------
>  7 files changed, 211 insertions(+), 83 deletions(-)
> 
> -- 
> 2.43.1



  parent reply	other threads:[~2024-03-12 18:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19 14:34 [PATCH v4 0/5] Virtio dmabuf improvements Albert Esteve
2024-02-19 14:34 ` [PATCH v4 1/5] hw/virtio: check owner for removing objects Albert Esteve
2024-02-19 14:34 ` [PATCH v4 2/5] hw/virtio: document SharedObject structures Albert Esteve
2024-02-20 10:28   ` Manos Pitsidianakis
2024-03-06 13:13     ` Albert Esteve
2024-02-19 14:34 ` [PATCH v4 3/5] hw/virtio: change dmabuf mutex to QemuMutex Albert Esteve
2024-02-20 10:34   ` Manos Pitsidianakis
2024-03-11 13:31     ` Albert Esteve
2024-03-12 20:47       ` Alex Bennée
2024-02-19 14:34 ` [PATCH v4 4/5] hw/virtio: cleanup shared resources Albert Esteve
2024-02-20 10:39   ` Manos Pitsidianakis
2024-03-12 18:13   ` Michael S. Tsirkin
2024-02-19 14:34 ` [PATCH v4 5/5] hw/virtio: rename virtio dmabuf API Albert Esteve
2024-03-12 18:23 ` Michael S. Tsirkin [this message]
2024-03-13  8:00   ` [PATCH v4 0/5] Virtio dmabuf improvements Albert Esteve

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=20240312142033-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=aesteve@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=kraxel@redhat.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=philmd@linaro.org \
    --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).