virtio — archive

[Rusty Russell <mst@redhat.com>]

"Michael S. Tsirkin" <mst@redhat.com> writes: > --- > content.tex | 6 ++++-- > 1 file changed, 4 insertions(+), 2 deletions(-) > > diff --git a/content.tex b/content.tex > index cbbad09..9902756 100644 > --- a/content.tex > +++ b/content.tex > @@ -1278,8 +1278,10 @@ enabled, device specific configuration starts at byte offset 20 in virtio > header. ie. once you enable MSI-X on the device, the other fields move. > If you turn it off again, they move back! > > -Immediately following these general headers, there may be > -device-specific headers: > +When using the legacy interface, both transitional > +devices and drivers MUST assume that > +the device-specific configuration space > +immediately follows these general headers: > > \begin{tabular}{|l||l|l|} > \hline > -- > MST "MUST assume" isn't a very good requirement. It's easier to simply describe it: Any device-specific configuration space immediately follows these general headers: Otherwise it needs to move into a normative subsection. Cheers, Rusty.