Skip to contentSkip to conversation

conformance: clarify transitional/non-transitional

PATCH Superseded Michael S. Tsirkin 1 participant 2 messages Mar 11, 2019

v2 of 4 Superseded Latest is v4 →

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 conformance: clarify transitional/non-transitional

Clarify that:
- non-transitional just satisfy 3 main clauses
- transitional also has a legacy interface:
however note that it's not an optional component *for transitional devices* so MAY is inappropriate
- legacy device descriptions are non-normative. In fact virtio 0.9 is non-normative as a whole and always was by design: it was early days and spec evolved to document bugs in implementations.

VIRTIO-167

---

Changes from v1:

Accept all changes proposed by Cornelia Huck <[email protected]>

 conformance.tex | 26 ++++++++++++++++++--------
 1 file changed, 18 insertions(+), 8 deletions(-)
conformance.tex +18 -8
index 1577c0c..518b9c7 100644
@@ -344,16 +344,26 @@ Interface: Terminology}.
 
 A non-transitional implementation conforms to this specification
 if it satisfies all of the MUST or REQUIRED level requirements
-defined above.
+defined in section \ref{sec:Conformance / Conformance Targets} above.
 
-An implementation MAY choose to implement OPTIONAL support for the
-legacy interface, including support for legacy drivers
-or devices, by additionally conforming to all of the MUST or
-REQUIRED level requirements for the legacy interface
-for the transitional devices and drivers.
+A transitional implementation conforms to this specification
+if it satisfies all of the MUST or REQUIRED level requirements
+defined in section \ref{sec:Conformance / Conformance Targets} above
+and additionally implements the legacy interface
+for the transitional devices and drivers, described in
+\hyperref[intro:Virtio PCI Draft]{[Virtio PCI Draft]}.
 
-The requirements for the legacy interface for transitional implementations
-are located in sections named ``Legacy Interface'' listed below:
+\begin{note}
+No normative specification for the legacy interface exists,
+instead device and driver's ability to interoperate with
+the existing body of installed devices and drivers is a quality
+of implementation issue.
+\begin{note}
+
+To facilitate creating transitional implementations, as well as
+assist in converting legacy interfaces to conforming ones,
+the requirements for the legacy interface for transitional implementations
+are located in non-normative sections named ``Legacy Interface'' listed below:
 \begin{itemize}
 \item Section \ref{sec:Basic Facilities of a Virtio Device /
 Feature Bits / Legacy Interface: A Note on Feature Bits}
Signature · 6 lines
MST

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
#1 lore raw
Quoted 10 lines · Michael S. Tsirkin

Clarify that:
- non-transitional just satisfy 3 main clauses
- transitional also has a legacy interface:
however note that it's not an optional component *for transitional devices* so MAY is inappropriate
- legacy device descriptions are non-normative. In fact virtio 0.9 is non-normative as a whole and always was by design: it was early days and spec evolved to document bugs in implementations.

Quoted 3 lines

VIRTIO-167

oops sent too soon. sorry will resend. pls ignore.

Quoted 50 lines

---

Changes from v1:

Accept all changes proposed by Cornelia Huck <[email protected]>

 conformance.tex | 26 ++++++++++++++++++--------
 1 file changed, 18 insertions(+), 8 deletions(-)
conformance.tex +18 -8
index 1577c0c..518b9c7 100644
@@ -344,16 +344,26 @@ Interface: Terminology}.
 
 A non-transitional implementation conforms to this specification
 if it satisfies all of the MUST or REQUIRED level requirements
-defined above.
+defined in section \ref{sec:Conformance / Conformance Targets} above.
 
-An implementation MAY choose to implement OPTIONAL support for the
-legacy interface, including support for legacy drivers
-or devices, by additionally conforming to all of the MUST or
-REQUIRED level requirements for the legacy interface
-for the transitional devices and drivers.
+A transitional implementation conforms to this specification
+if it satisfies all of the MUST or REQUIRED level requirements
+defined in section \ref{sec:Conformance / Conformance Targets} above
+and additionally implements the legacy interface
+for the transitional devices and drivers, described in
+\hyperref[intro:Virtio PCI Draft]{[Virtio PCI Draft]}.
 
-The requirements for the legacy interface for transitional implementations
-are located in sections named ``Legacy Interface'' listed below:
+\begin{note}
+No normative specification for the legacy interface exists,
+instead device and driver's ability to interoperate with
+the existing body of installed devices and drivers is a quality
+of implementation issue.
+\begin{note}
+
+To facilitate creating transitional implementations, as well as
+assist in converting legacy interfaces to conforming ones,
+the requirements for the legacy interface for transitional implementations
+are located in non-normative sections named ``Legacy Interface'' listed below:
 \begin{itemize}
 \item Section \ref{sec:Basic Facilities of a Virtio Device /
 Feature Bits / Legacy Interface: A Note on Feature Bits}
Signature · 1 line
MST

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php