virtio — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
[PATCH RFC v7 0/8] Introduce device group and device management
On 8/12/2022 8:19 PM, Michael S. Tsirkin wrote:
> ensures forward and backward compatibility as long as
> we tuck new structures at the end.
>
> Signed-off-by: Michael S. Tsirkin <[email protected]>
> ---
>
admin.tex | 6 ++++++
>
1 file changed, 6 insertions(+)
>
> diff --git a/admin.tex b/admin.tex
> index a0008c7..99b6c2a 100644
> --- a/admin.tex
> +++ b/admin.tex
> @@ -136,6 +136,12 @@ \subsection{Group administration commands}\label{sec:Basic Facilities of a Virti
>
holds the command specific error. If \field{status} is not set to VIRTIO_ADMIN_STATUS_CS_ERR, the
>
\field{command_specific_error} value is undefined and should be ignored by the driver.
>
> +It is legal for the driver to submit commands with device-writeable and
> +device-readable structures both shorter and longer than what
> +is described in this specification. Device silently truncates the
> +structures to the shorter of the two (submitted by driver and
> +described in this specification).
> +
Why not limit this to only allow submitting longer structure provided by
the driver ?
If the structures are shorter, return some error code that we will
define (VIRTIO_ADMIN_STATUS_READABLE_DATA_SHORT,
VIRTIO_ADMIN_STATUS_WRITABLE_DATA_SHORT).
Shorter data buffers can provide partial description to the device.
I'm trying not to restrict ourselves with this definition.
Driver that will start getting weird errors will not know what to do and
why something went wrong.
>
\section{Administration Virtqueue}\label{sec:Basic Facilities of a Virtio Device / Group Administration Virtqueues}
>
>
An administration virtqueue of a parent device is used to submit
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]