From: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
To: virtio-dev@lists.oasis-open.org,
virtio-comment@lists.oasis-open.org, stefanha@redhat.com,
cohuck@redhat.com
Cc: vgoyal@redhat.com
Subject: [virtio-comment] [PATCH v5 0/5] Large shared memory regions
Date: Thu, 27 Jun 2019 20:28:25 +0100 [thread overview]
Message-ID: <20190627192830.5285-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 five parts:
a) A general definition of the idea
b) An addition of an 'id' field to allow multiple distinct
capabilities of the same type.
c) An addition of a 64bit capability type.
d) A definition on virtio-pci using the layout previously
discussed.
e) A definition on virtio-mmio.
v5:
Based on Michael's comments, the 'id' field is now moved into
the main virtio_pci_cap, and the 64 bit cpaaibility is now a more
general type.
Minor other rewordings.
Dr. David Alan Gilbert (5):
shared memory: Define shared memory regions
pci: Define id field
pci: Define virtio_pci_cap64
shared memory: Define PCI capability
shared memory: Define mmio registers
conformance.tex | 1 +
content.tex | 77 ++++++++++++++++++++++++++++++++++++++++++++++++-
shared-mem.tex | 42 +++++++++++++++++++++++++++
3 files changed, 119 insertions(+), 1 deletion(-)
create mode 100644 shared-mem.tex
--
2.21.0
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-06-27 19:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 19:28 Dr. David Alan Gilbert (git) [this message]
2019-06-27 19:28 ` [virtio-comment] [PATCH v5 1/5] shared memory: Define shared memory regions Dr. David Alan Gilbert (git)
2019-07-03 13:13 ` [virtio-comment] " Cornelia Huck
2019-06-27 19:28 ` [virtio-comment] [PATCH v5 2/5] pci: Define id field Dr. David Alan Gilbert (git)
2019-06-28 10:00 ` [virtio-comment] " Cornelia Huck
2019-06-28 13:36 ` [virtio-comment] Re: [virtio-dev] " Dr. David Alan Gilbert
2019-07-03 13:04 ` Cornelia Huck
2019-07-10 17:45 ` Dr. David Alan Gilbert
2019-06-27 19:28 ` [virtio-comment] [PATCH v5 3/5] pci: Define virtio_pci_cap64 Dr. David Alan Gilbert (git)
2019-06-28 10:02 ` [virtio-comment] " Cornelia Huck
2019-06-27 19:28 ` [virtio-comment] [PATCH v5 4/5] shared memory: Define PCI capability Dr. David Alan Gilbert (git)
2019-07-03 13:23 ` [virtio-comment] " Cornelia Huck
2019-07-10 17:49 ` Dr. David Alan Gilbert
2019-06-27 19:28 ` [virtio-comment] [PATCH v5 5/5] shared memory: Define mmio registers Dr. David Alan Gilbert (git)
2019-07-03 13:26 ` [virtio-comment] " Cornelia Huck
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=20190627192830.5285-1-dgilbert@redhat.com \
--to=dgilbert@redhat.com \
--cc=cohuck@redhat.com \
--cc=stefanha@redhat.com \
--cc=vgoyal@redhat.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 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.