From: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
To: virtio-comment@lists.oasis-open.org, virtio-dev@lists.oasis-open.org
Cc: stefanha@redhat.com, cohuck@redhat.com, sebastien.boeuf@intel.com
Subject: [virtio-comment] [PATCH v3 0/3] Large shared memory regions
Date: Mon, 4 Mar 2019 13:25:28 +0000 [thread overview]
Message-ID: <20190304132531.10507-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 v3 addresses most feedback on v2. The MMIO registers have
changed a bit based on feedback (in particular from Sebastien
who has been trying it out).
Dave
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-04 13:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 13:25 Dr. David Alan Gilbert (git) [this message]
2019-03-04 13:25 ` [virtio-comment] [PATCH v3 1/3] shared memory: Define shared memory regions Dr. David Alan Gilbert (git)
2019-03-05 17:54 ` [virtio-comment] " Cornelia Huck
2019-03-07 16:25 ` [virtio-comment] " Stefan Hajnoczi
2019-03-07 17:53 ` Dr. David Alan Gilbert
2019-03-08 9:18 ` Stefan Hajnoczi
2019-03-04 13:25 ` [virtio-comment] [PATCH v3 2/3] shared memory: Define PCI capability Dr. David Alan Gilbert (git)
2019-03-07 16:28 ` [virtio-comment] " Stefan Hajnoczi
2019-03-07 18:24 ` Dr. David Alan Gilbert
2019-03-08 9:19 ` Stefan Hajnoczi
2019-03-04 13:25 ` [virtio-comment] [PATCH v3 3/3] shared memory: Define mmio registers Dr. David Alan Gilbert (git)
2019-03-07 16:28 ` [virtio-comment] " Stefan Hajnoczi
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=20190304132531.10507-1-dgilbert@redhat.com \
--to=dgilbert@redhat.com \
--cc=cohuck@redhat.com \
--cc=sebastien.boeuf@intel.com \
--cc=stefanha@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.