From e0ce988563106c29a5d88219b92ee63eb79a8cc7 Mon Sep 17 00:00:00 2001 From: mstsirkin Date: Wed, 22 Apr 2015 11:25:38 +0000 Subject: cl: document VIRTIO-137 Signed-off-by: Michael S. Tsirkin git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio/branches/v1.0@513 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652 --- cl-os.tex | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) (limited to 'cl-os.tex') diff --git a/cl-os.tex b/cl-os.tex index 05b6dfa..6ae3180 100644 --- a/cl-os.tex +++ b/cl-os.tex @@ -83,3 +83,29 @@ Initialization And Device Operation / Device Initialization / Non-transitional Device With Legacy Driver}. } \\ \hline +504 & 22 Apr 2015 & Rusty Russell & {VIRTIO-137: +define the meaning and requirements of the len field. + +We said what it was for, and noted why. We didn't place any +requirements on it, nor clearly spell out the implications of its use. + +This clarification comes particularly from noticing that QEMU +didn't set len correctly, and philosophising over the correct value +when an error has occurred. +See \ref{sec:Basic Facilities of a Virtio Device / Virtqueues / +The Virtqueue Used Ring}, \ref{devicenormative:Basic Facilities +of a Virtio Device / Virtqueues / The Virtqueue Used Ring} and +\ref{sec:Basic Facilities of a Virtio Device / Virtqueues / The +Virtqueue Used Ring}. + } \\ +\hline +510 & 22 Apr 2015 & Michael Tsirkin & {conformance: +add VIRTIO-137 statement links + +Add links to new conformance statements added to +resolve VIRTIO-137 (describing used ring entry len usage). + +See \ref{sec:Conformance / Device Conformance} +and \ref{sec:Conformance / Driver Conformance}. + } \\ +\hline -- cgit v1.2.3