From: David Stevens <stevensd@chromium.org>
To: virtio-comment@lists.oasis-open.org
Cc: "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>,
"David Stevens" <stevensd@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: [PATCH v4 0/2] Cross-device resource sharing
Date: Thu, 19 Mar 2020 11:18:21 +0900 [thread overview]
Message-ID: <20200319021823.57219-1-stevensd@chromium.org> (raw)
Hi all,
This is the next iteration of patches for adding support for sharing
resources between different virtio devices. The corresponding Linux
implementation is [1].
In addition to these patches, the most recent virtio-video patchset
includes a patch for importing objects into that device [2].
[1] https://markmail.org/thread/bfy6uk4q4v4cus7h
[2] https://markmail.org/message/wxdne5re7aaugbjg
Changes v3 -> v4:
- Add virtio-gpu feature bit
- Move virtio-gpu assign uuid command into 2d command group
- Rename virtio-gpu uuid response
David Stevens (2):
content: define what an exported object is
virtio-gpu: add the ability to export resources
content.tex | 12 ++++++++++++
introduction.tex | 4 ++++
virtio-gpu.tex | 29 +++++++++++++++++++++++++++++
3 files changed, 45 insertions(+)
--
2.25.1.481.gfbce0eb801-goog
next reply other threads:[~2020-03-19 2:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 2:18 David Stevens [this message]
2020-03-19 2:18 ` [PATCH v4 1/2] content: define what an exported object is David Stevens
2020-03-19 2:18 ` [PATCH v4 2/2] virtio-gpu: add the ability to export resources David Stevens
2020-03-20 6:41 ` [PATCH v4 0/2] Cross-device resource sharing Gerd Hoffmann
2020-03-23 1:52 ` David Stevens
2020-04-28 2:15 ` [virtio-comment] Request vote for the patch: " David Stevens
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=20200319021823.57219-1-stevensd@chromium.org \
--to=stevensd@chromium.org \
--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=tfiga@chromium.org \
--cc=virtio-comment@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 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).