conformance: hook up GPU device normative statements
PATCH 1/1 conformance: hook up GPU device normative statements
These statements already exist, but were not linked in the conformance section.
---
I think this one can go in as an editorial update, at it just seems to have been missed.
However, I think we need to go over the GPU spec: it seems to have a lot of MUST etc. language that is not in any normative section. No driver normative sections also seem to point to some possible omissions. Probably 1.3 material, though.
--- conformance.tex | 10 ++++++++++ 1 file changed, 10 insertions(+)
conformance.tex +10 -0
@@ -48,6 +48,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets} \ref{sec:Conformance / Device Conformance / Entropy Device Conformance}, \ref{sec:Conformance / Device Conformance / Traditional Memory Balloon Device Conformance}, \ref{sec:Conformance / Device Conformance / SCSI Host Device Conformance}, +\ref{sec:Conformance / Device Conformance / GPU Device Conformance}, \ref{sec:Conformance / Device Conformance / Input Device Conformance}, \ref{sec:Conformance / Device Conformance / Crypto Device Conformance}, \ref{sec:Conformance / Device Conformance / Socket Device Conformance},
@@ -453,6 +454,15 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets} \item \ref{devicenormative:Device Types / SCSI Host Device / Device Operation / Device Operation: eventq} \end{itemize} +\conformance{\subsection}{GPU Device Conformance}\label{sec:Conformance / Device Conformance / GPU Device Conformance} + +A GPU device MUST conform to the following normative statements: + +\begin{itemize} +\item \ref{devicenormative:Device Types / GPU Device / Device Initialization} +\item \ref{devicenormative:Device Types / GPU Device / Device Operation / Device Operation: Command lifecycle and fencing} +\end{itemize} + \conformance{\subsection}{Input Device Conformance}\label{sec:Conformance / Device Conformance / Input Device Conformance} An input device MUST conform to the following normative statements:
Signature · 1 line
2.34.1
Quoted 8 lines · Cornelia Huck
These statements already exist, but were not linked in the conformance section.
Signed-off-by Cornelia Huck <[email protected]>---
I think this one can go in as an editorial update, at it just seems to have been missed.
Quoted 8 lines
However, I think we need to go over the GPU spec: it seems to have a lot of MUST etc. language that is not in any normative section. No driver normative sections also seem to point to some possible omissions. Probably 1.3 material, though.
--- conformance.tex | 10 ++++++++++ 1 file changed, 10 insertions(+)
Pushed as editorial update.
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: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
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/