Re: [virtio-comment] [PATCH v1 1/2] virtio-mem: introduce VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE

[Cornelia Huck <cohuck@redhat.com>]

On Tue, Aug 17 2021, David Hildenbrand <david@redhat.com> wrote:

> On 17.08.21 11:23, Cornelia Huck wrote:
>> On Tue, Aug 17 2021, David Hildenbrand <david@redhat.com> wrote:
>> 
>>> On 17.08.21 10:50, Cornelia Huck wrote:
>>>> On Thu, Aug 12 2021, David Hildenbrand <david@redhat.com> wrote:
>>>>> +With VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE, the device MAY allow the CPU to
>>>>
>>>> "If VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE has been negotiated, ..."
>>>>
>>>
>>> ack
>>>
>>>>> +read memory of unplugged memory blocks inside \field{usable_region_size}.
>>>>
>>>> A compliant driver would not read that memory, would it?
>>>
>>> Indeed. The device could decide to allow for reading, but it's pretty
>>> much undefined behavior.
>> 
>> Maybe make it "SHOULD NOT"? Less strong than "MUST NOT", but still makes
>> clear that a driver reading it is pretty much doing the wrong thing.
>> 
>
> I was also wondering to just drop it completely, because it's actually 
> undefined behavior. What do you think?

Right, I'm not sure we need to specify this at all. Do others have an
opinion? The one thing it does is adding a nicely symmetrical statement.


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/