Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: virtio-dev@lists.oasis-open.org,
	virtio-comment@lists.oasis-open.org, stefanha@redhat.com,
	vgoyal@redhat.com
Subject: [virtio-comment] Re: [PATCH v5 1/5] shared memory: Define shared memory regions
Date: Wed, 3 Jul 2019 15:13:20 +0200	[thread overview]
Message-ID: <20190703151320.4d22f2b5.cohuck@redhat.com> (raw)
In-Reply-To: <20190627192830.5285-2-dgilbert@redhat.com>

On Thu, 27 Jun 2019 20:28:26 +0100
"Dr. David Alan Gilbert (git)" <dgilbert@redhat.com> wrote:

> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> 
> Define the requirements and idea behind shared memory regions.
> 
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
>  conformance.tex |  1 +
>  content.tex     |  2 ++
>  shared-mem.tex  | 42 ++++++++++++++++++++++++++++++++++++++++++
>  3 files changed, 45 insertions(+)
>  create mode 100644 shared-mem.tex

Reviewed-by: Cornelia Huck <cohuck@redhat.com>

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-03 13:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27 19:28 [virtio-comment] [PATCH v5 0/5] Large shared memory regions Dr. David Alan Gilbert (git)
2019-06-27 19:28 ` [virtio-comment] [PATCH v5 1/5] shared memory: Define " Dr. David Alan Gilbert (git)
2019-07-03 13:13   ` Cornelia Huck [this message]
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=20190703151320.4d22f2b5.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=dgilbert@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox