From: David Hildenbrand <david@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>, virtio-comment@lists.oasis-open.org
Cc: Hui Zhu <teawater@gmail.com>,
Marek Kedzierski <mkedzier@redhat.com>,
Sebastien Boeuf <sebastien.boeuf@intel.com>,
Halil Pasic <pasic@linux.ibm.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Pankaj Gupta <pankaj.gupta.linux@gmail.com>,
Wei Yang <richard.weiyang@linux.alibaba.com>
Subject: Re: [PATCH RESEND v2 0/5] virtio-mem: VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE and interaction with memory properties
Date: Fri, 24 Sep 2021 12:01:47 +0200 [thread overview]
Message-ID: <843ec36a-e682-017c-2343-7571ac7b3fcb@redhat.com> (raw)
In-Reply-To: <87h7ebe2b9.fsf@redhat.com>
On 23.09.21 17:31, Cornelia Huck wrote:
> On Mon, Sep 20 2021, David Hildenbrand <david@redhat.com> wrote:
>
>> Looking into supporting virtio-mem
>> a) without a shared zeropage for the memory backing of the device --
>> not allowing the driver to read unplugged memory
>> b) on architectures with memory properties for RAM (e.g., s390x with
>> storage keys and storage attributes)
>> requires extension of the spec to handle both cases cleanly and describe
>> the expected semantics.
>>
>> I'll open a github issue soon; in the meantime, I'll work on the actual
>> implementation in QEMU and Linux.
>
> LGTM, but would like a second opinion.
Thanks Conny! I'll wait for more feedback before I open a github issue /
request a vote.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-09-24 10:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 13:46 [PATCH RESEND v2 0/5] virtio-mem: VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE and interaction with memory properties David Hildenbrand
2021-09-20 13:46 ` [PATCH RESEND v2 1/5] virtio-mem: simplify statements that express unexpected behavior on memory access David Hildenbrand
2021-09-23 11:55 ` [virtio-comment] " Cornelia Huck
2021-09-20 13:46 ` [PATCH RESEND v2 2/5] virtio-mem: rephrase remaining memory access statements David Hildenbrand
2021-09-23 11:56 ` [virtio-comment] " Cornelia Huck
2021-09-20 13:46 ` [virtio-comment] [PATCH RESEND v2 3/5] virtio-mem: document basic memory access to plugged memory blocks David Hildenbrand
2021-09-23 12:02 ` Cornelia Huck
2021-09-20 13:46 ` [PATCH RESEND v2 4/5] virtio-mem: introduce VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE David Hildenbrand
2021-09-23 12:10 ` [virtio-comment] " Cornelia Huck
2021-09-20 13:46 ` [PATCH RESEND v2 5/5] virtio-mem: describe interaction with memory properties David Hildenbrand
2021-09-23 15:29 ` [virtio-comment] " Cornelia Huck
2021-09-23 15:31 ` [virtio-comment] Re: [PATCH RESEND v2 0/5] virtio-mem: VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE and " Cornelia Huck
2021-09-24 10:01 ` David Hildenbrand [this message]
2021-10-06 10:59 ` Cornelia Huck
2021-10-06 11:00 ` David Hildenbrand
2021-10-06 11:09 ` [virtio-comment] " Cornelia Huck
2021-10-06 12:48 ` 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=843ec36a-e682-017c-2343-7571ac7b3fcb@redhat.com \
--to=david@redhat.com \
--cc=cohuck@redhat.com \
--cc=jasowang@redhat.com \
--cc=mkedzier@redhat.com \
--cc=mst@redhat.com \
--cc=pankaj.gupta.linux@gmail.com \
--cc=pasic@linux.ibm.com \
--cc=richard.weiyang@linux.alibaba.com \
--cc=sebastien.boeuf@intel.com \
--cc=teawater@gmail.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