summaryrefslogtreecommitdiff
path: root/content.tex
diff options
context:
space:
mode:
authormstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>2014-03-02 21:37:05 +0000
committermstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>2014-03-02 21:37:05 +0000
commit757d875793dc1ee523b3d2ebe59512148e3fa941 (patch)
tree38986c34fb69277edc3ae71bad98c4cd0323cd22 /content.tex
parent7232c520616404bdccb084c9058551b0ef4b82f1 (diff)
feedback: clarify device status bits
Change accepted on VIRTIO TC Meeting, 3 December 2013 VIRTIO-70 Cc: Patrick Durusau <patrick@durusau.net> Signed-off-by: Michael S. Tsirkin <mst@redhat.com> git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@304 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
Diffstat (limited to 'content.tex')
-rw-r--r--content.tex16
1 files changed, 12 insertions, 4 deletions
diff --git a/content.tex b/content.tex
index c9a566a..c98648b 100644
--- a/content.tex
+++ b/content.tex
@@ -13,12 +13,16 @@ device consists of the following parts:
\end{itemize}
\section{\field{Device Status} Field}\label{sec:Basic Facilities of a Virtio Device / Device Status Field}
+During device initialization by a driver,
+the driver follows the sequence of steps specified in
+\ref{sec:General Initialization And Device Operation / Device
+Initialization}.
The \field{device status} field provides a simple low-level
-diagnostic: it's most useful to imagine them hooked up to traffic
+indication of the completed steps of this sequence.
+It's most useful to imagine it hooked up to traffic
lights on the console indicating the status of each device. The
following bits are defined:
-
\begin{description}
\item[ACKNOWLEDGE (1)] Indicates that the guest OS has found the
device and recognized it as a valid virtio device.
@@ -41,8 +45,12 @@ following bits are defined:
\end{description}
\drivernormative{\subsection}{Device Status Field}{Basic Facilities of a Virtio Device / Device Status Field}
-The driver MUST update \field{device status} in the order above to
-indicate the driver's progress. The driver MUST NOT clear a
+The driver MUST update \field{device status},
+setting bits to indicate the completed steps of the driver
+initialization sequence specified in
+\ref{sec:General Initialization And Device Operation / Device
+Initialization}.
+The driver MUST NOT clear a
\field{device status} bit. If the driver sets the FAILED bit,
it MUST reset the device before attempting to re-initialize.