From: Cornelia Huck <cohuck@redhat.com>
To: Albert Esteve <aesteve@redhat.com>, qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Albert Esteve <aesteve@redhat.com>
Subject: Re: [PATCH 1/4] virtio-dmabuf: introduce virtio-dmabuf
Date: Mon, 08 May 2023 15:12:09 +0200 [thread overview]
Message-ID: <87o7mvc6hi.fsf@redhat.com> (raw)
In-Reply-To: <20230503081911.119168-2-aesteve@redhat.com>
On Wed, May 03 2023, Albert Esteve <aesteve@redhat.com> wrote:
> This API manages objects (in this iteration,
> dmabuf fds) that can be shared along different
> virtio devices.
>
> The API allows the different devices to add,
> remove and/or retrieve the objects by simply
> invoking the public functions that reside in the
> virtio-dmabuf file.
>
> Signed-off-by: Albert Esteve <aesteve@redhat.com>
> ---
> hw/display/meson.build | 1 +
> hw/display/virtio-dmabuf.c | 88 +++++++++++++++++++++++
> include/hw/virtio/virtio-dmabuf.h | 58 ++++++++++++++++
> tests/unit/meson.build | 1 +
> tests/unit/test-virtio-dmabuf.c | 112 ++++++++++++++++++++++++++++++
> 5 files changed, 260 insertions(+)
> create mode 100644 hw/display/virtio-dmabuf.c
> create mode 100644 include/hw/virtio/virtio-dmabuf.h
> create mode 100644 tests/unit/test-virtio-dmabuf.c
>
> diff --git a/hw/display/meson.build b/hw/display/meson.build
> index 17165bd536..62a27395c0 100644
> --- a/hw/display/meson.build
> +++ b/hw/display/meson.build
> @@ -37,6 +37,7 @@ softmmu_ss.add(when: 'CONFIG_MACFB', if_true: files('macfb.c'))
> softmmu_ss.add(when: 'CONFIG_NEXTCUBE', if_true: files('next-fb.c'))
>
> softmmu_ss.add(when: 'CONFIG_VGA', if_true: files('vga.c'))
> +softmmu_ss.add(when: 'CONFIG_VIRTIO', if_true: files('virtio-dmabuf.c'))
>
> if (config_all_devices.has_key('CONFIG_VGA_CIRRUS') or
> config_all_devices.has_key('CONFIG_VGA_PCI') or
> diff --git a/hw/display/virtio-dmabuf.c b/hw/display/virtio-dmabuf.c
> new file mode 100644
General comment: new files should be covered in MAINTAINERS; not sure if
there is any generic section that could match it, or if this should go
into a new section.
> index 0000000000..3db939a2e3
> --- /dev/null
> +++ b/hw/display/virtio-dmabuf.c
Is virtio-dmabuf only useful for stuff under display/, or could it go
into a more generic section?
next prev parent reply other threads:[~2023-05-08 13:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 8:19 [PATCH 0/4] Virtio shared dma-buf Albert Esteve
2023-05-03 8:19 ` [PATCH 1/4] virtio-dmabuf: introduce virtio-dmabuf Albert Esteve
2023-05-08 13:12 ` Cornelia Huck [this message]
2023-05-09 7:21 ` Albert Esteve
2023-05-09 10:52 ` Marc-André Lureau
2023-05-09 12:52 ` Albert Esteve
2023-05-09 12:57 ` Marc-André Lureau
2023-05-17 15:10 ` Albert Esteve
2023-05-03 8:19 ` [PATCH 2/4] vhost-user: add shared_object msg Albert Esteve
2023-05-03 8:19 ` [PATCH 3/4] vhost-user: refactor send_resp code Albert Esteve
2023-05-03 8:19 ` [PATCH 4/4] libvhost-user: add write_msg cb to dev struct Albert Esteve
2023-05-09 10:11 ` Marc-André Lureau
2023-05-09 11:17 ` Albert Esteve
2023-05-09 12:53 ` Marc-André Lureau
2023-05-10 12:30 ` 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=87o7mvc6hi.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=aesteve@redhat.com \
--cc=mst@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).