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: [RFC PATCH v3 0/2] Cross-device resource sharing
Date: Fri, 7 Feb 2020 16:40:31 +0900 [thread overview]
Message-ID: <20200207074033.172289-1-stevensd@chromium.org> (raw)
Hi all,
This is the next iteration of patches for adding support for sharing
resources between different virtio devices. In addition to these
patches, the most recent virtio-video patchset includes a patch for
importing objects into that device [1].
[1] https://markmail.org/message/wxdne5re7aaugbjg
Changes v2 -> v3:
* Replace references to guest/host
* Remove unnecessary paragraph and field in exported object section
* Recommend RFC4122 version 4 UUIDs
* Represent UUID as u8[16] instead of le64 pair
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.0.341.g760bfbb309-goog
next reply other threads:[~2020-02-07 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 7:40 David Stevens [this message]
2020-02-07 7:40 ` [RFC PATCH v3 1/2] content: define what an exported object is David Stevens
2020-02-07 7:40 ` [RFC PATCH v3 2/2] virtio-gpu: add the ability to export resources David Stevens
2020-02-12 11:50 ` 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=20200207074033.172289-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).