Return-Path: Subject: Re: [PATCH RESEND v2 0/5] virtio-mem: VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE and interaction with memory properties References: <20210920134653.16412-1-david@redhat.com> <87h7ebe2b9.fsf@redhat.com> From: David Hildenbrand Message-ID: <843ec36a-e682-017c-2343-7571ac7b3fcb@redhat.com> Date: Fri, 24 Sep 2021 12:01:47 +0200 MIME-Version: 1.0 In-Reply-To: <87h7ebe2b9.fsf@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit To: Cornelia Huck , virtio-comment@lists.oasis-open.org Cc: Hui Zhu , Marek Kedzierski , Sebastien Boeuf , Halil Pasic , "Michael S. Tsirkin" , Jason Wang , Pankaj Gupta , Wei Yang List-ID: On 23.09.21 17:31, Cornelia Huck wrote: > On Mon, Sep 20 2021, David Hildenbrand 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