summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>2014-03-05 14:16:47 +0000
committermstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>2014-03-05 14:16:47 +0000
commit0a10ee72e63bbfe358c47c9bccc11d4d10ad49f1 (patch)
tree2b4fe51a76babca9d28d6fa1cf16a981b6a6d34f
parent77cb18f8f2763e28d9a40abcc677c36b9d213050 (diff)
legacy devices: get rid of MUST assume
as Rusty points out MUST assume is not very good requirement. clarify it. git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@312 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
-rw-r--r--content.tex15
1 files changed, 11 insertions, 4 deletions
diff --git a/content.tex b/content.tex
index 439a972..973a2e7 100644
--- a/content.tex
+++ b/content.tex
@@ -1451,10 +1451,8 @@ enabled, device specific configuration starts at byte offset 20 in virtio
header. ie. once you enable MSI-X on the device, the other fields move.
If you turn it off again, they move back!
-When using the legacy interface, both transitional
-devices and drivers MUST assume that
-the device-specific configuration space
-immediately follows these general headers:
+Any device-specific configuration space immediately follows
+these general headers:
\begin{tabular}{|l||l|l|}
\hline
@@ -1466,6 +1464,15 @@ Purpose & Device Specific & \\
\hline
\end{tabular}
+When accessing the device-specific configuration space
+using the legacy interface, transitional
+drivers MUST access the device-specific configuration space
+at an offset immediately following the general headers.
+
+When using the legacy interface, transitional
+devices MUST present the device-specific configuration space
+if any at an offset immediately following the general headers.
+
Note that only Feature Bits 0 to 31 are accessible through the
Legacy Interface. When used through the Legacy Interface,
Transitional Devices MUST assume that Feature Bits 32 to 63