virtio — archive

[Pawel Moll]

Fix minor typos as reported in ARM's feedback. Signed-off-by: Pawel Moll <pawel.moll@arm.com> --- content.tex 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content.tex b/content.tex index 2f09419..ed72cde 100644 --- a/content.tex +++ b/content.tex @@ -168,7 +168,7 @@ space. drivernormative{subsection}{Device Configuration Space}{Basic Facilities of a Virtio Device / Device Configuration Space} Drivers MUST NOT assume reads from -fields greater than 32 bits wide are atomic, nor reads from +fields greater than 32 bits wide are atomic, nor are reads from multiple fields: drivers SHOULD read device configuration space fields like so: egin{lstlisting} @@ -216,7 +216,7 @@ The correct endian-ness is documented 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 field{capacity} (see ef{sec:Device Types / +affects the block field{capacity} (see ef{sec:Device Types / Block Device / Feature bits / Device configuration layout}) and network field{mac} (see ef{sec:Device Types / Network Device / Device configuration layout}) fields; @@ -3642,7 +3642,7 @@ compartibility. drivernormative{subparagraph}{Setting Offloads State}{Device Types / Network Device / Device Operation / Control Virtqueue / Offloads State Configuration / Setting Offloads State} -A driver MUST NOT enable a offload for which the appropriate feature +A driver MUST NOT enable an offload for which the appropriate feature has not been negotiated. subparagraph{Legacy Interface: Setting Offloads State}label{sec:Device Types / Network Device / Device Operation / Control Virtqueue / Offloads State Configuration / Setting Offloads State / Legacy Interface: Setting Offloads State} -- 1.9.1