Let's cleanly document that the driver just has to allow for access to
plugged memory blocks.
Signed-off-by: David Hildenbrand <redacted>
---
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/