All of lore.kernel.org
 help / color / mirror / Atom feed
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 v7 0/5] Large shared memory regions
Date: Fri, 12 Jul 2019 13:19:57 +0100	[thread overview]
Message-ID: <20190712122002.10793-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.
 
v7:
  Conformance reference from Cornelia's review

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 |  2 ++
 content.tex     | 83 +++++++++++++++++++++++++++++++++++++++++++++++--
 shared-mem.tex  | 42 +++++++++++++++++++++++++
 3 files changed, 125 insertions(+), 2 deletions(-)
 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/


             reply	other threads:[~2019-07-12 12:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12 12:19 Dr. David Alan Gilbert (git) [this message]
2019-07-12 12:19 ` [virtio-comment] [PATCH v7 1/5] shared memory: Define shared memory regions Dr. David Alan Gilbert (git)
2019-07-12 12:19 ` [virtio-comment] [PATCH v7 2/5] pci: Define id field Dr. David Alan Gilbert (git)
2019-07-12 12:20 ` [virtio-comment] [PATCH v7 3/5] pci: Define virtio_pci_cap64 Dr. David Alan Gilbert (git)
2019-07-29 15:40   ` [virtio-dev] " Nikos Dragazis
2019-07-29 15:48     ` [virtio-comment] " Dr. David Alan Gilbert
2019-07-31 12:12       ` [virtio-dev] [PATCH] content: fix typo Nikos Dragazis
2019-07-31 12:18         ` Cornelia Huck
2019-07-12 12:20 ` [virtio-comment] [PATCH v7 4/5] shared memory: Define PCI capability Dr. David Alan Gilbert (git)
2019-07-12 12:48   ` [virtio-comment] " Cornelia Huck
2019-07-12 13:41     ` Dr. David Alan Gilbert
2019-07-12 12:20 ` [virtio-comment] [PATCH v7 5/5] 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=20190712122002.10793-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.