[virtio-comment] Re: [PATCH RESEND v2 0/5] virtio-mem: VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE and interaction with memory properties

From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@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: [virtio-comment] Re: [PATCH RESEND v2 0/5] virtio-mem: VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE and interaction with memory properties
Date: Wed, 06 Oct 2021 13:09:41 +0200	[thread overview]
Message-ID: <87k0iqz9xm.fsf@redhat.com> (raw)
In-Reply-To: <d4fb2e98-931d-d53f-a24f-3d48ea3fc1ad@redhat.com>

On Wed, Oct 06 2021, David Hildenbrand <david@redhat.com> wrote:

> On 06.10.21 12:59, Cornelia Huck wrote:
>> On Fri, Sep 24 2021, David Hildenbrand <david@redhat.com> wrote:
>> 
>>> 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.
>> 
>> Anyone else interested in looking at this?
>> 
>> Otherwise, I'd say just open an issue and request a vote.
>> 
>
> Would it make sense to split it into two parts?
>
> VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE: #1-#4
> Memory properties: #5
>
> Then I could resend via the split and request two votes.

From my POV, this can go in via one vote[*]. We can also split this up,
if you think that makes sense.

[*] Less votes == less work for me :)

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/