OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [PATCH 03/14] Legacy Interface: Device Configuration Space

legacy has no generation field.
add SHOULD statement to document multi-byte field
access rules.

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
 content.tex | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/content.tex b/content.tex
index 3942350..deee9e4 100644
--- a/content.tex
+++ b/content.tex
@@ -200,7 +200,11 @@ The correct endian-ness is documented explicitly for each device.
 Legacy devices did not have a configuration generation field, thus are
 susceptible to race conditions if configuration is updated.  This
-effects the block capacity and network mac fields; best practice is to
+effects the block \field{capacity} (see \ref{sec:Device Types /
+Block Device / Feature bits / Device configuration layout}) and
+network \field{mac} (see \ref{sec:Device Types / Network Device /
+Device configuration layout}) fields;
+when using the legacy interface, drivers SHOULD
 read these fields multiple times until two reads generate a consistent

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]