> From: Cornelia Huck <coh...@redhat.com>
> Sent: Wednesday, February 22, 2023 8:27 AM
> > We can just skip adding a new requirement completely - we'll never get
> > there with a compliant driver. This is what we do e.g. for MMIO.
> > Why not?
>
> That would be fine with me as well.
>
> > This has an advantage as this allows backing config with regular RAM.
> > Also I feel that since it always said "read only for driver" then this
> > implies a restriction on driver not the device.
>
> Indeed. The normative statement below should be enough to make that "read-
> only for the driver" thing obvious.
>
> >
> >> >
> >> >
> >> >> >
> >> >> >>
> >> >> >> Driver section:
> >> >> >> Driver must not write to read-only fields.
> >> >>
> >> >> "The driver MUST NOT write to any config space field."
I addressed the comments in v4 at [1].
[1] https://lists.oasis-open.org/archives/virtio-dev/202302/msg00523.html
Please review.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
