Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
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
Subject: [virtio-comment] [PATCH v2 0/3] Large shared memory regions
Date: Fri, 22 Feb 2019 11:54:30 +0000	[thread overview]
Message-ID: <20190222115433.7160-1-dgilbert@redhat.com> (raw)

From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>

Hi,
  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 is untested
however I thought best to include it since it shows that
it isn't tied to PCI.


This v2 addresses (hopefully all) comments from the initial posting,
except for CCW and the GPU/dynamic usage currently being
discussed by Frank.  Cornelia has a suggested approach for CCW
that is being discussed, so it looks like we're getting there on
that.  The GPU usage being discussed by Frank is diverging to a
very different usage.

Dave

Dr. David Alan Gilbert (3):
  shared memory: Define shared memory regions
  shared memory: Define PCI capability
  shared memory: Define mmio registers

 content.tex    | 71 ++++++++++++++++++++++++++++++++++++++++++++++++++
 shared-mem.tex | 33 +++++++++++++++++++++++
 2 files changed, 104 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/


             reply	other threads:[~2019-02-22 11:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22 11:54 Dr. David Alan Gilbert (git) [this message]
2019-02-22 11:54 ` [virtio-comment] [PATCH v2 1/3] shared memory: Define shared memory regions Dr. David Alan Gilbert (git)
2019-02-22 12:48   ` [virtio-comment] " Cornelia Huck
2019-02-25 16:37     ` Stefan Hajnoczi
2019-02-26 15:11     ` [virtio-comment] Re: [virtio-dev] " Dr. David Alan Gilbert
2019-02-26 15:40       ` Halil Pasic
2019-02-26 15:43       ` Cornelia Huck
2019-03-04 12:46         ` Dr. David Alan Gilbert
2019-02-22 11:54 ` [virtio-comment] [PATCH v2 2/3] shared memory: Define PCI capability Dr. David Alan Gilbert (git)
2019-02-22 12:50   ` [virtio-comment] " Cornelia Huck
2019-02-22 11:54 ` [virtio-comment] [PATCH v2 3/3] shared memory: Define mmio registers Dr. David Alan Gilbert (git)
2019-02-25 16:50   ` [virtio-comment] " Stefan Hajnoczi
2019-02-25 18:45     ` Dr. David Alan Gilbert
2019-02-27 13:56       ` Cornelia Huck
2019-02-27 17:06         ` Stefan Hajnoczi
2019-02-27 18:37           ` [virtio-comment] Re: [virtio-dev] " Dr. David Alan Gilbert
2019-02-27 18:52             ` Dr. David Alan Gilbert
2019-02-27 13:50   ` Cornelia Huck
2019-02-27 18:33     ` [virtio-comment] Re: [virtio-dev] " Dr. David Alan Gilbert
2019-03-05 15:47 ` [virtio-comment] [PATCH v2 0/3] Large shared memory regions Frank Yang
2019-06-17 18:38   ` Michael S. Tsirkin
2019-06-17 18:59     ` Frank Yang

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=20190222115433.7160-1-dgilbert@redhat.com \
    --to=dgilbert@redhat.com \
    --cc=cohuck@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox