From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: virtio-comment@lists.oasis-open.org,
teawater <teawaterz@linux.alibaba.com>,
Marek Kedzierski <mkedzier@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>
Subject: [virtio-comment] Re: [PATCH v1] virtio-mem: minor clarification regarding read-access to unplugged blocks
Date: Fri, 20 Nov 2020 16:13:30 +0100 [thread overview]
Message-ID: <20201120161330.740d694e.cohuck@redhat.com> (raw)
In-Reply-To: <20201116191629.47661-1-david@redhat.com>
On Mon, 16 Nov 2020 20:16:29 +0100
David Hildenbrand <david@redhat.com> wrote:
> 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(-)
Looks reasonable to me.
Acked-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/
next prev parent reply other threads:[~2020-11-20 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` Cornelia Huck [this message]
2020-11-27 10:39 ` [virtio-comment] " 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
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=20201120161330.740d694e.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=mkedzier@redhat.com \
--cc=mst@redhat.com \
--cc=teawaterz@linux.alibaba.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