From: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
To: virtio-dev@lists.oasis-open.org, virtio-comment@lists.oasis-open.org
Cc: stefanha@redha.com, cohuck@redhat.com
Subject: [virtio-comment] [PATCH v4 0/3] Large shared memory regions
Date: Wed, 20 Mar 2019 12:07:37 +0000 [thread overview]
Message-ID: <20190320120740.8514-1-dgilbert@redhat.com> (raw)
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
This series formalises the idea of shared memory regions I'd
previously discussed and is intended for use with virtio-fs.
I've split it into three parts:
a) A general definition of the idea
b) A definition on virtio-pci using the layout previously
discussed; this still uses the list of capabilities.
c) A definition on virtio-mmio.
This v4 has one small tweak to the addressing comment in
patch 1, based partially on Stefan's feedback to v3.
Dr. David Alan Gilbert (3):
shared memory: Define shared memory regions
shared memory: Define PCI capability
shared memory: Define mmio registers
conformance.tex | 1 +
content.tex | 69 +++++++++++++++++++++++++++++++++++++++++++++++++
shared-mem.tex | 40 ++++++++++++++++++++++++++++
3 files changed, 110 insertions(+)
create mode 100644 shared-mem.tex
--
2.20.1
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next reply other threads:[~2019-03-20 12:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 12:07 Dr. David Alan Gilbert (git) [this message]
2019-03-20 12:07 ` [virtio-comment] [PATCH v4 1/3] shared memory: Define shared memory regions Dr. David Alan Gilbert (git)
2019-06-17 18:30 ` Michael S. Tsirkin
2019-06-19 16:06 ` Dr. David Alan Gilbert
2019-06-19 16:24 ` Michael S. Tsirkin
2019-06-21 20:42 ` Michael S. Tsirkin
2019-06-27 16:35 ` [virtio-comment] Re: [virtio-dev] " Dr. David Alan Gilbert
2019-03-20 12:07 ` [virtio-comment] [PATCH v4 2/3] shared memory: Define PCI capability Dr. David Alan Gilbert (git)
2019-06-17 18:36 ` [virtio-comment] Re: [virtio-dev] " Michael S. Tsirkin
2019-06-17 18:41 ` Michael S. Tsirkin
2019-06-19 17:13 ` Dr. David Alan Gilbert
2019-06-20 5:45 ` Michael S. Tsirkin
2019-06-21 20:38 ` [virtio-comment] Re: [virtio-dev] " Michael S. Tsirkin
2019-06-19 17:10 ` Dr. David Alan Gilbert
2019-06-20 5:43 ` Michael S. Tsirkin
2019-06-21 20:39 ` Michael S. Tsirkin
2019-03-20 12:07 ` [virtio-comment] [PATCH v4 3/3] shared memory: Define mmio registers Dr. David Alan Gilbert (git)
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=20190320120740.8514-1-dgilbert@redhat.com \
--to=dgilbert@redhat.com \
--cc=cohuck@redhat.com \
--cc=stefanha@redha.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.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