summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorrusty <rusty@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>2014-02-26 03:20:20 +0000
committerrusty <rusty@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>2014-02-26 03:20:20 +0000
commit86e4e22fcb381dcb8cd9a795b527676b4d46e577 (patch)
treef23161957b9f88d50d3e34cf05ed9a26c001c20c
parent0ab234cbdddb5750f6d5f28b485550a10575e9c0 (diff)
Feedback: 2.1 Device Status field: Separate description from normative.
Start with explanation, progress to normative requirements. Signed-off-by: Rusty Russell <rusty@au1.ibm.com> git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@264 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
-rw-r--r--content.tex21
1 files changed, 12 insertions, 9 deletions
diff --git a/content.tex b/content.tex
index cb090dd..6ab0caa 100644
--- a/content.tex
+++ b/content.tex
@@ -14,13 +14,10 @@ device consists of the following parts:
\section{\field{Device Status} Field}\label{sec:Basic Facilities of a Virtio Device / Device Status Field}
-The driver MUST update the \field{device status} field in the order below to
-indicate its progress. This provides a simple low-level diagnostic:
-it's most useful to imagine them hooked up to traffic lights on the
-console indicating the status of each device. The driver MUST NOT
-clear a \field{device status} bit.
-
-\field{device status} is 0 upon reset, otherwise at least one bit should be set:
+The \field{device status} field provides a simple low-level
+diagnostic: it's most useful to imagine them 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
@@ -40,10 +37,16 @@ clear a \field{device status} bit.
\item[FAILED (128)] Indicates that something went wrong in the guest,
and it has given up on the device. This could be an internal
error, or the driver didn't like the device for some reason, or
- even a fatal error during device operation. The driver MUST
- reset the device before attempting to re-initialize.
+ even a fatal error during device operation.
\end{description}
+The driver MUST update \field{device status} in the order above to
+indicate the driver's progress. 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.
+
+The device MUST initialize \field{device status} to 0 upon reset.
+
\section{Feature Bits}\label{sec:Basic Facilities of a Virtio Device / Feature Bits}
Each virtio device offers all the features it understands. During