Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: virtio-comment@lists.oasis-open.org
Cc: David Hildenbrand <david@redhat.com>
Subject: [virtio-comment] [PATCH v2 3/5] virtio-mem: document basic memory access to plugged memory blocks
Date: Mon, 20 Sep 2021 15:36:16 +0200	[thread overview]
Message-ID: <20210920133618.16071-4-david@redhat.com> (raw)
In-Reply-To: <20210920133618.16071-1-david@redhat.com>

Let's cleanly document that the driver just has to allow for access to
plugged memory blocks.

Signed-off-by: David Hildenbrand <david@redhat.com>
---
 virtio-mem.tex | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/virtio-mem.tex b/virtio-mem.tex
index cca3c9f..3860b8c 100644
--- a/virtio-mem.tex
+++ b/virtio-mem.tex
@@ -249,6 +249,9 @@ \subsection{Device Operation}\label{sec:Device Types / Memory Device / Device Op
 
 The device MUST NOT change the content of plugged memory blocks.
 
+The device MUST allow the driver to read and write memory of plugged
+memory blocks.
+
 The device MUST allow the driver to read memory of unplugged memory blocks
 inside \field{usable_region_size} via the CPU. \footnote{To allow for simplified
 dumping of memory. The CPU is expected to copy such memory to another location
-- 
2.31.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/


  parent reply	other threads:[~2021-09-20 13:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-20 13:36 [PATCH v2 0/5] virtio-mem: VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE and interaction with memory properties David Hildenbrand
2021-09-20 13:36 ` [virtio-comment] [PATCH v2 1/5] virtio-mem: simplify statements that express unexpected behavior on memory access David Hildenbrand
2021-09-20 13:36 ` [virtio-comment] [PATCH v2 2/5] virtio-mem: rephrase remaining memory access statements David Hildenbrand
2021-09-20 13:36 ` David Hildenbrand [this message]
2021-09-20 13:36 ` [virtio-comment] [PATCH v2 4/5] virtio-mem: introduce VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE David Hildenbrand
2021-09-20 13:36 ` [virtio-comment] [PATCH v2 5/5] virtio-mem: describe interaction with memory properties 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=20210920133618.16071-4-david@redhat.com \
    --to=david@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