Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: virtio-comment@lists.oasis-open.org
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
	Cornelia Huck <cohuck@redhat.com>,
	David Hildenbrand <david@redhat.com>
Subject: [virtio-comment] [PATCH v2 0/3] virtio-spec: Add virtio-mem device specification
Date: Thu, 18 Jun 2020 10:21:47 +0200	[thread overview]
Message-ID: <20200618082150.17476-1-david@redhat.com> (raw)

Add the specification for virtio-mem devices. The Linux driver is part
of v5.8-rc1. The latest QEMU implementation (v4) can be found at [1].

[1] https://lkml.kernel.org/r/20200610115419.51688-1-david@redhat.com

v1 -> v2:
- Adapt to configuration layout change (block_size is now 64 bit)
- Some minor rephrasings

David Hildenbrand (3):
  conformance: make driver conformance list easier to read and maintain
  conformance: Reference RPMB Driver Conformance
  Add virtio-mem device specification

 conformance.tex |  47 ++++-
 content.tex     |   1 +
 virtio-mem.tex  | 448 ++++++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 493 insertions(+), 3 deletions(-)
 create mode 100644 virtio-mem.tex

-- 
2.26.2


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:[~2020-06-18  8:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18  8:21 David Hildenbrand [this message]
2020-06-18  8:21 ` [virtio-comment] [PATCH v2 1/3] conformance: make driver conformance list easier to read and maintain David Hildenbrand
2020-06-18  8:21 ` [virtio-comment] [PATCH v2 2/3] conformance: Reference RPMB Driver Conformance David Hildenbrand
2020-06-19 17:51   ` Alex Bennée
2020-06-18  8:21 ` [virtio-comment] [PATCH v2 3/3] Add virtio-mem device specification David Hildenbrand
2020-07-07 11:56 ` [virtio-comment] Re: [PATCH v2 0/3] virtio-spec: " David Hildenbrand
2020-07-20  9:17 ` David Hildenbrand

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=20200618082150.17476-1-david@redhat.com \
    --to=david@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=mst@redhat.com \
    --cc=virtio-comment@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