From: Gerd Hoffmann <kraxel@redhat.com>
To: David Stevens <stevensd@chromium.org>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
"Michael S . Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
virtualization@lists.linux-foundation.org,
linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org,
virtio-dev@lists.oasis-open.org
Subject: Re: [PATCH 1/2] virtio: add dma-buf support for exported objects
Date: Tue, 25 Feb 2020 07:10:08 +0100 [thread overview]
Message-ID: <20200225061008.wqxqppfglzmwvtid@sirius.home.kraxel.org> (raw)
In-Reply-To: <20200219080637.61312-2-stevensd@chromium.org>
On Wed, Feb 19, 2020 at 05:06:36PM +0900, David Stevens wrote:
> This change adds a new flavor of dma-bufs that can be used by virtio
> drivers to share exported objects. A virtio dma-buf can be queried by
> virtio drivers to obtain the UUID which identifies the underlying
> exported object.
That duplicates a bunch of code from dma-buf.c in virtio_dma_buf.c.
How about dma_buf_{get,set}_uuid, simliar to dma_buf_set_name?
cheers,
Gerd
WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com>
To: David Stevens <stevensd@chromium.org>
Cc: virtio-dev@lists.oasis-open.org,
"Michael S . Tsirkin" <mst@redhat.com>,
David Airlie <airlied@linux.ie>, Jason Wang <jasowang@redhat.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
virtualization@lists.linux-foundation.org,
linaro-mm-sig@lists.linaro.org, linux-media@vger.kernel.org
Subject: Re: [PATCH 1/2] virtio: add dma-buf support for exported objects
Date: Tue, 25 Feb 2020 07:10:08 +0100 [thread overview]
Message-ID: <20200225061008.wqxqppfglzmwvtid@sirius.home.kraxel.org> (raw)
In-Reply-To: <20200219080637.61312-2-stevensd@chromium.org>
On Wed, Feb 19, 2020 at 05:06:36PM +0900, David Stevens wrote:
> This change adds a new flavor of dma-bufs that can be used by virtio
> drivers to share exported objects. A virtio dma-buf can be queried by
> virtio drivers to obtain the UUID which identifies the underlying
> exported object.
That duplicates a bunch of code from dma-buf.c in virtio_dma_buf.c.
How about dma_buf_{get,set}_uuid, simliar to dma_buf_set_name?
cheers,
Gerd
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com>
To: David Stevens <stevensd@chromium.org>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
"Michael S . Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
virtualization@lists.linux-foundation.org,
linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org,
virtio-dev@lists.oasis-open.org
Subject: [virtio-dev] Re: [PATCH 1/2] virtio: add dma-buf support for exported objects
Date: Tue, 25 Feb 2020 07:10:08 +0100 [thread overview]
Message-ID: <20200225061008.wqxqppfglzmwvtid@sirius.home.kraxel.org> (raw)
In-Reply-To: <20200219080637.61312-2-stevensd@chromium.org>
On Wed, Feb 19, 2020 at 05:06:36PM +0900, David Stevens wrote:
> This change adds a new flavor of dma-bufs that can be used by virtio
> drivers to share exported objects. A virtio dma-buf can be queried by
> virtio drivers to obtain the UUID which identifies the underlying
> exported object.
That duplicates a bunch of code from dma-buf.c in virtio_dma_buf.c.
How about dma_buf_{get,set}_uuid, simliar to dma_buf_set_name?
cheers,
Gerd
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2020-02-25 6:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 8:06 [PATCH 0/2] Support virtio cross-device resources David Stevens
2020-02-19 8:06 ` [virtio-dev] " David Stevens
2020-02-19 8:06 ` David Stevens
2020-02-19 8:06 ` [PATCH 1/2] virtio: add dma-buf support for exported objects David Stevens
2020-02-19 8:06 ` [virtio-dev] " David Stevens
2020-02-19 8:06 ` David Stevens
2020-02-25 6:10 ` Gerd Hoffmann [this message]
2020-02-25 6:10 ` [virtio-dev] " Gerd Hoffmann
2020-02-25 6:10 ` Gerd Hoffmann
2020-02-26 3:56 ` [virtio-dev] " David Stevens
2020-02-26 3:56 ` David Stevens
2020-02-26 3:56 ` David Stevens
2020-02-26 3:56 ` David Stevens
2020-02-26 16:07 ` [virtio-dev] " Gerd Hoffmann
2020-02-26 16:07 ` Gerd Hoffmann
2020-02-26 16:07 ` Gerd Hoffmann
2020-02-19 8:06 ` [PATCH 2/2] drm/virtio: Support virtgpu exported resources David Stevens
2020-02-19 8:06 ` [virtio-dev] " David Stevens
2020-02-19 8:06 ` David Stevens
2020-02-25 6:15 ` Gerd Hoffmann
2020-02-25 6:15 ` [virtio-dev] " Gerd Hoffmann
2020-02-25 6:15 ` Gerd Hoffmann
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=20200225061008.wqxqppfglzmwvtid@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jasowang@redhat.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mst@redhat.com \
--cc=stevensd@chromium.org \
--cc=sumit.semwal@linaro.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.