OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [PATCH v2 6/7] introduction.tex: introduce a glossary of terms

On Fri, Jul 24, 2020 at 04:42:50PM +0100, Alex Bennée wrote:
> +\subsection{Glossary}\label{intro:Glossary}
> +
> +The following are definitions of common terms used throughout the specification.
> +
> +\begin{description}
> +\item[Device] The series of configuration, control and operation
> +  mechanisms that make a Virtio device. The implementation details of

This definition is self-referential.

How about:

  The embodiment of a device type consisting of configuration space,
  virtqueues, and a transport.

This also requires defining "device type":

  A set of configuration space and virtqueue structure definitions that
  offer I/O functionality.

> +  the device should be transparent to the Driver.

I'm not sure about this "should" statement. Maybe this concept can be
worked into the first sentence or dropped. "May", "can", "should",
"must" are only used in the normative spec sections.

Attachment: signature.asc
Description: PGP signature

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]