summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>2016-02-16 17:31:33 +0000
committermstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>2016-02-16 17:31:33 +0000
commitcf56d824c88b9707b1db7e591661aebdf67ede60 (patch)
tree0268107e23ae796f8e0f3e08513f4b8e28d66be1
parenta510be931481d7cf08e9f9a055f815e9fca11a50 (diff)
cl: list changes since CSPRD05
Signed-off-by: Michael S. Tsirkin <mst@redhat.com> git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio/branches/v1.0@565 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
-rw-r--r--cl-os.tex56
1 files changed, 56 insertions, 0 deletions
diff --git a/cl-os.tex b/cl-os.tex
index aee28d6..da78bf8 100644
--- a/cl-os.tex
+++ b/cl-os.tex
@@ -76,3 +76,59 @@ This resolves VIRTIO-146.
See \ref{sec:Transition from earlier specification drafts}.
} \\
\hline
+554 & 16 Feb 2016 & Thomas Huth & {virtio-net: fix inconsistent legacy header size
+
+ Current text says:
+ The legacy driver only presented num_buffers in the struct
+ virtio_net_hdr when VIRTIO_NET_F_MRG_RXBUF was not negotiated;
+
+ Should be:
+ "\dots was negotiated \dots" instead of "\dots was not negotiated \dots"
+
+ To be consistent with the following:
+ without that feature the structure was 2 bytes shorter.
+
+See \ref{sec:Device Types / Network Device / Device Operation / Legacy Interface: Device Operation}.
+} \\
+\hline
+555 & 16 Feb 2016 & Michael S. Tsirkin & {virtio header: tweak
+change motivation
+
+ The changes are not just to remove Linux assumptions,
+ we have also renamed ring->queue.
+ Tweak the header description accordingly.
+
+See \ref{sec:Basic Facilities of a Virtio Device / Virtqueues / Helpers for Operating Virtqueues}.
+} \\
+\hline
+558 & 16 Feb 2016 & Michael S. Tsirkin & {rename virtio_ring.h to virtio_queue.h
+
+ Since vring* and VRING* have been replaced with virtq* and VIRTQ*
+ respectively, rename the header virtio_ring.h to virtio_queue.h.
+
+See \ref{sec:virtio-queue.h}.
+} \\
+\hline
+559 & 16 Feb 2016 & Michael S. Tsirkin & {init: sort status bits
+
+ Status bit order is inconsistent: they are neither in increasing
+ order nor in the order they are likely to be used.
+
+ The second approach seems more useful since there aren't
+ that many bits, so the numerical order does not help much.
+
+ A typical order of use would be:
+
+\begin{itemize}
+\item ACKNOWLEDGE
+\item DRIVER
+\item then either FAILED or FEATURES_OK
+\item then either FAILED or DRIVER_OK
+\item then DEVICE_NEEDS_RESET (if device detects an error)
+\end{itemize}
+
+ Sort the bits accordingly.
+
+See \ref{sec:Basic Facilities of a Virtio Device / Device Status Field}.
+} \\
+\hline