abstract: address lnovich comment

lnovich@redhat.com suggested rewording abstract,
making the following point:

. from what point of view is virtio like a physical device?
  it's very different from host POV
. "the guest" appears out of nowhere. It's the guest that runs
  in the vm of course.
. "not all that different" means similar so there's not need to
  be verbose

Address this comment

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@245 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
introduction: address lnovich comments

generally list of buses is out of date, list all supported buses.
Drop explicit mention of lguest since it's not part of the spec.

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@246 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
content: more strict confirmance language

Correct new language to explicitly use MAY/SHOULD/MUST
in more places or simply drop the somewhat vague "can" where
we are describing the only way to operate the device.
Most of the changes are in the PCI section.

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@247 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
PCI: minor wording change

Since access width requirement is a confirmance clause, make it
explicit that it applies to 4,2 and 1 byte fields.
Also explain what happens to fields of other widths (such as
the 6 byte MAC).

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@248 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
ccw: padding annotations

Remove __packed__ annotation from all ccw structures that don't need it,
and make the length requirements explicit for those that do.

This is the part of the patch to resolve VIRTIO-56 that had been missed.

Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>

git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@249 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
net: fix incorrect reference.

It pointed into the block section for some reason.

Signed-off-by: Rusty Russell <rusty@au1.ibm.com>

git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@250 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
Gratuitous Packet Sending: clarify wording.

The device can ask, not the driver.

Signed-off-by: Rusty Russell <rusty@au1.ibm.com>

git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@251 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
feedback: minor wording cleanups

We already mention requirement for natural width
accesses for non device specific configuration.
Don't repeat this in legacy section.

Further, mention virtio pci structure in
preamble to help link sections together.

Cc: Arun Subbarao <asubbarao@lnxw.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

Conflicts:
	content.tex
PCI: better document driver and device requirements

Feedback:
10) 4.1.3.1.2 Queue Vector Configuration
Some of the information from section 8.4 needs to be moved to
here, for example that the device may have an MSI-X table size
other than 2048.
Otherwise, this reads as though the MSI-X table must always have
2048 entries.

11) Please explicitly describe the device behavior when writing
a vector value beyond the MSI-X table size.

Address these comments.

Cc: Arun Subbarao <asubbarao@lnxw.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Feedback: TAB-557 Spelling errors, etc.

Reported-by: Patrick Durusau <patrick@durusau.net>
Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
Feedback: TAB-555 Bad sub-sectioning

Reported-by: Patrick Durusau <patrick@durusau.net>
Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
Feedback: Bug TAB-553

Haven't marked them non-normative yet, but it makes sense to put the header
in an appendix.

Reported-by: Patrick Durusau <patrick@durusau.net>
Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
Feedback: move new device design section to Appendix.

It's non-normative.

Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
Feedback: use proper list in introduction.

Also avoid extra spacing before footnote markers.

Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
Feedback: add old draft to normative references.

Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
Feedback: hoist the one legacy-related requirement out of legacy section.

This requirement applies to any system which *did* have legacy drivers.

Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
Feedback: move legacy/transitional definitions into terminology.

Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
Feedback: 2.1 Device Status field: Separate description from normative.

Start with explanation, progress to normative requirements.

Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
Feedback: add normative marker.

From http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html:
   Normative statements MUST be referenceable so that a statement may be
   referenced from another part of a specification, but more importantly
   so they can be referenced from Conformance Clauses.

Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
Feedback: split Basic Facilities feature bits and config space into normative.

Split text into descriptive and normative.

Signed-off-by: Rusty Russell <rusty@au1.ibm.com>