virtio — archive

[PATCH 00/14] VIRTIO-71: conformance clauses for legacy interface

From: Rusty Russell <[email protected]>
To: [email protected]
Date: Tue, 25 Feb 2014 01:53:00 -0000

"Michael S. Tsirkin" <[email protected]> writes: > We don't want to maintain 0.9.X - much better if > virtio 1.0 can supercede it - so we must include > the conformance statements for the legacy interface > directly in 1.0. Our original goal was to do exactly this, and have a document on how to handle the differences. I was going to propose we move it to an appendix and make all the legacy sections into "Note: Legacy:" notes. But 90% of my reason was that I didn't want to do the work :) You've done most of it already, so I don't mind as much. Cheers, Rusty. > Explain that we have an optional transitional > module with a set of requiremenents, and > that these are limited > to transitional devices. > > Addresses > VIRTIO-71 > > Michael S. Tsirkin (14): > content: explain that legacy support is optional > legacy: clarify general note on endian-ness > Legacy Interface: Device Configuration Space > legacy: make note on legacy VQ endian-ness normative > legacy: make message framing normative > legacy pci layout: confirmance statements > legacy pci layout: extra confirmance statement > leacy: layout detection confirmance > legacy feature bits: confirmance statements > legacy: make all notes on endian-ness confirmance clauses > legacy virtqueue layout: confirmance > legacy device initialization: confirmance statements > conformance: document two types of devices > non-transitional devices with legacy drivers > > conformance.tex | 58 +++++++++++- > content.tex | 267 +++++++++++++++++++++++++++++++++++++++ ----------------- > 2 files changed, 241 insertions(+), 84 deletions(-) > > -- > MST > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected]