All of lore.kernel.org
 help / color / mirror / Atom feed
* [virtio-comment] [PATCH v1] virtio-mem: minor clarification regarding read-access to unplugged blocks
@ 2020-11-16 19:16 David Hildenbrand
  2020-11-20 15:13 ` [virtio-comment] " Cornelia Huck
  2020-12-02 10:30 ` [virtio-comment] " David Hildenbrand
  0 siblings, 2 replies; 7+ messages in thread
From: David Hildenbrand @ 2020-11-16 19:16 UTC (permalink / raw)
  To: virtio-comment
  Cc: David Hildenbrand, teawater, Marek Kedzierski,
	Michael S . Tsirkin, Cornelia Huck

Let's clarify that we don't expect all DMA to work with unplugged blocks.
We really only give guarantees when reading from unplugged memory blocks
via the CPU, e.g., as done by Linux when creating a system dump via
kdump: the new kernel will copy the content of the old (crashed) kernel
via the CPU to user space, from where it will find its final destination
inside the dump file. Note that dumping via makedumpfile under Linux will
avoid reading unplugged blocks completely.

This is a preparation for device passthrough to VMs, whereby such
dedicated devices might not be able to read from unplugged memory blocks.

Let's document that this scenario is possible, and why this handling is
in place at all.

Cc: teawater <teawaterz@linux.alibaba.com>
Cc: Marek Kedzierski <mkedzier@redhat.com>
Cc: Michael S. Tsirkin <mst@redhat.com>
Cc: Cornelia Huck <cohuck@redhat.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
---
 virtio-mem.tex | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/virtio-mem.tex b/virtio-mem.tex
index 85cfb61..62a1d02 100644
--- a/virtio-mem.tex
+++ b/virtio-mem.tex
@@ -246,8 +246,13 @@ \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 to read from unplugged memory blocks inside
-the usable device-managed region.
+The device MUST allow the CPU to read from unplugged memory blocks inside
+the usable device-managed region. \footnote{To allow for simplified dumping of
+memory. The CPU is expected to copy such memory to another location before
+starting DMA.}
+
+The device MAY allow to read from unplugged memory blocks inside the
+usable device-managed region via DMA.
 
 The device MAY allow to read from unplugged memory blocks outside
 the usable device-managed region.
-- 
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/


^ permalink raw reply related	[flat|nested] 7+ messages in thread
end of thread, other threads:[~2020-12-02 10:30 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-11-16 19:16 [virtio-comment] [PATCH v1] virtio-mem: minor clarification regarding read-access to unplugged blocks David Hildenbrand
2020-11-20 15:13 ` [virtio-comment] " Cornelia Huck
2020-11-27 10:39   ` David Hildenbrand
2020-11-27 11:02     ` Cornelia Huck
2020-12-02  9:25       ` David Hildenbrand
2020-12-02 10:15         ` Cornelia Huck
2020-12-02 10:30 ` [virtio-comment] " David Hildenbrand

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.