From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Stevens <stevensd@chromium.org>
Cc: virtio-dev@lists.oasis-open.org,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Dylan Reid" <dgreid@chromium.org>,
"Tomasz Figa" <tfiga@chromium.org>,
"Zach Reizner" <zachr@chromium.org>,
"Keiichi Watanabe" <keiichiw@chromium.org>,
"Alexandre Courbot" <acourbot@chromium.org>,
"Alex Lau" <alexlau@chromium.org>,
"Stéphane Marchesin" <marcheu@chromium.org>,
"Pawel Osciak" <posciak@chromium.org>,
"Gurchetan Singh" <gurchetansingh@chromium.org>,
"Stefan Hajnoczi" <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Linux Media Mailing List" <linux-media@vger.kernel.org>
Subject: Re: [virtio-dev][RFC PATCH v2 0/2] Cross-device resource sharing
Date: Wed, 22 Jan 2020 03:24:02 -0500 [thread overview]
Message-ID: <20200122032328-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAD=HUj71Z_eQUj93LZYOAc+Prj9ohym1oJtiLWzCy5=T-cNxCQ@mail.gmail.com>
On Wed, Jan 22, 2020 at 04:16:15PM +0900, David Stevens wrote:
> This RFC comes from the recent discussion on buffer sharing [1],
> specifically about the need to share resources between different
> virtio devices. For a concrete use case, this can be used to share
> virtio-gpu allocated buffers with the recently proposed virtio video
> device [2], without the need to memcpy decoded frames through the
> guest.
>
> [1] https://markmail.org/thread/jeh5xjjxvylyrbur
> [2] https://markmail.org/thread/yb25fim2dqfuktgf
Wrong list- this belongs on virtio-comment.
dev is for implementation discussions.
> Changes v1 -> v2:
> Rename exported resource to exported object
> Rename the virtio-gpu export command
>
> David Stevens (2):
> content: define what an exported object is
> virtio-gpu: add the ability to export resources
>
> content.tex | 18 ++++++++++++++++++
> virtio-gpu.tex | 30 ++++++++++++++++++++++++++++++
> 2 files changed, 48 insertions(+)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Stevens <stevensd@chromium.org>
Cc: virtio-dev@lists.oasis-open.org,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Dylan Reid" <dgreid@chromium.org>,
"Tomasz Figa" <tfiga@chromium.org>,
"Zach Reizner" <zachr@chromium.org>,
"Keiichi Watanabe" <keiichiw@chromium.org>,
"Alexandre Courbot" <acourbot@chromium.org>,
"Alex Lau" <alexlau@chromium.org>,
"Stéphane Marchesin" <marcheu@chromium.org>,
"Pawel Osciak" <posciak@chromium.org>,
"Gurchetan Singh" <gurchetansingh@chromium.org>,
"Stefan Hajnoczi" <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Linux Media Mailing List" <linux-media@vger.kernel.org>
Subject: Re: [virtio-dev][RFC PATCH v2 0/2] Cross-device resource sharing
Date: Wed, 22 Jan 2020 03:24:02 -0500 [thread overview]
Message-ID: <20200122032328-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAD=HUj71Z_eQUj93LZYOAc+Prj9ohym1oJtiLWzCy5=T-cNxCQ@mail.gmail.com>
On Wed, Jan 22, 2020 at 04:16:15PM +0900, David Stevens wrote:
> This RFC comes from the recent discussion on buffer sharing [1],
> specifically about the need to share resources between different
> virtio devices. For a concrete use case, this can be used to share
> virtio-gpu allocated buffers with the recently proposed virtio video
> device [2], without the need to memcpy decoded frames through the
> guest.
>
> [1] https://markmail.org/thread/jeh5xjjxvylyrbur
> [2] https://markmail.org/thread/yb25fim2dqfuktgf
Wrong list- this belongs on virtio-comment.
dev is for implementation discussions.
> Changes v1 -> v2:
> Rename exported resource to exported object
> Rename the virtio-gpu export command
>
> David Stevens (2):
> content: define what an exported object is
> virtio-gpu: add the ability to export resources
>
> content.tex | 18 ++++++++++++++++++
> virtio-gpu.tex | 30 ++++++++++++++++++++++++++++++
> 2 files changed, 48 insertions(+)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Stevens <stevensd@chromium.org>
Cc: virtio-dev@lists.oasis-open.org,
"Zach Reizner" <zachr@chromium.org>,
"Alexandre Courbot" <acourbot@chromium.org>,
qemu-devel <qemu-devel@nongnu.org>,
"Stefan Hajnoczi" <stefanha@gmail.com>,
"Alex Lau" <alexlau@chromium.org>,
"Tomasz Figa" <tfiga@chromium.org>,
"Keiichi Watanabe" <keiichiw@chromium.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Stéphane Marchesin" <marcheu@chromium.org>,
"Dylan Reid" <dgreid@chromium.org>,
"Gurchetan Singh" <gurchetansingh@chromium.org>,
"Pawel Osciak" <posciak@chromium.org>,
"Linux Media Mailing List" <linux-media@vger.kernel.org>
Subject: Re: [virtio-dev][RFC PATCH v2 0/2] Cross-device resource sharing
Date: Wed, 22 Jan 2020 03:24:02 -0500 [thread overview]
Message-ID: <20200122032328-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAD=HUj71Z_eQUj93LZYOAc+Prj9ohym1oJtiLWzCy5=T-cNxCQ@mail.gmail.com>
On Wed, Jan 22, 2020 at 04:16:15PM +0900, David Stevens wrote:
> This RFC comes from the recent discussion on buffer sharing [1],
> specifically about the need to share resources between different
> virtio devices. For a concrete use case, this can be used to share
> virtio-gpu allocated buffers with the recently proposed virtio video
> device [2], without the need to memcpy decoded frames through the
> guest.
>
> [1] https://markmail.org/thread/jeh5xjjxvylyrbur
> [2] https://markmail.org/thread/yb25fim2dqfuktgf
Wrong list- this belongs on virtio-comment.
dev is for implementation discussions.
> Changes v1 -> v2:
> Rename exported resource to exported object
> Rename the virtio-gpu export command
>
> David Stevens (2):
> content: define what an exported object is
> virtio-gpu: add the ability to export resources
>
> content.tex | 18 ++++++++++++++++++
> virtio-gpu.tex | 30 ++++++++++++++++++++++++++++++
> 2 files changed, 48 insertions(+)
>
> ---------------------------------------------------------------------
> 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-01-22 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 7:16 [virtio-dev][RFC PATCH v2 0/2] Cross-device resource sharing David Stevens
2020-01-22 7:16 ` David Stevens
2020-01-22 8:24 ` Michael S. Tsirkin [this message]
2020-01-22 8:24 ` Michael S. Tsirkin
2020-01-22 8:24 ` Michael S. Tsirkin
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=20200122032328-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=acourbot@chromium.org \
--cc=alexlau@chromium.org \
--cc=dgreid@chromium.org \
--cc=gurchetansingh@chromium.org \
--cc=keiichiw@chromium.org \
--cc=kraxel@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=marcheu@chromium.org \
--cc=posciak@chromium.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stevensd@chromium.org \
--cc=tfiga@chromium.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=zachr@chromium.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.