Skip to content

Commit 8a2ca3a

Browse files
virtio-msg: propose common-spec integration text
Update common-spec text so Virtio Over Messages is referenced from the core device facilities and introduction. This is a proposal for changes in the virtio common specification to properly insert the virtio message transport in the transport-neutral text. Keep the change minimal for now: - update content.tex to mention Virtio Over Messages in the transport list and in VIRTIO_F_ADMIN_VQ text - update introduction.tex to mention message-based transports We could also adapt newtransport.tex, but that is intentionally left out here to keep the proposal minimal. Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>
1 parent 19d50b0 commit 8a2ca3a

2 files changed

Lines changed: 13 additions & 6 deletions

File tree

content.tex

Lines changed: 12 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,9 @@ \chapter{Basic Facilities of a Virtio Device}\label{sec:Basic Facilities of a Vi
22

33
A virtio device is discovered and identified by a bus-specific method
44
(see the bus specific sections: \ref{sec:Virtio Transport Options / Virtio Over PCI Bus}~\nameref{sec:Virtio Transport Options / Virtio Over PCI Bus},
5-
\ref{sec:Virtio Transport Options / Virtio Over MMIO}~\nameref{sec:Virtio Transport Options / Virtio Over MMIO} and \ref{sec:Virtio Transport Options / Virtio Over Channel I/O}~\nameref{sec:Virtio Transport Options / Virtio Over Channel I/O}). Each
5+
\ref{sec:Virtio Transport Options / Virtio Over MMIO}~\nameref{sec:Virtio Transport Options / Virtio Over MMIO},
6+
\ref{sec:Virtio Transport Options / Virtio Over Channel I/O}~\nameref{sec:Virtio Transport Options / Virtio Over Channel I/O}
7+
and \ref{sec:Virtio Transport Options / Virtio Over Messages}~\nameref{sec:Virtio Transport Options / Virtio Over Messages}). Each
68
device consists of the following parts:
79

810
\begin{itemize}
@@ -931,11 +933,16 @@ \chapter{Reserved Feature Bits}\label{sec:Reserved Feature Bits}
931933

932934
\item[VIRTIO_F_ADMIN_VQ(41)] This feature indicates that the device exposes one or more
933935
administration virtqueues.
934-
At the moment this feature is only supported for devices using
935-
\ref{sec:Virtio Transport Options / Virtio Over PCI
936+
Devices using \ref{sec:Virtio Transport Options / Virtio Over PCI
936937
Bus}~\nameref{sec:Virtio Transport Options / Virtio Over PCI Bus}
937-
as the transport and is reserved for future use for
938-
devices using other transports (see
938+
expose administration virtqueues using the transport-specific
939+
fields defined by that transport. Devices using
940+
\ref{sec:Virtio Transport Options / Virtio Over Messages}~\nameref{sec:Virtio Transport Options / Virtio Over Messages}
941+
expose administration virtqueues through the device information
942+
reported by that transport.
943+
944+
For devices using other transports, this feature is reserved for
945+
future use (see
939946
\ref{drivernormative:Basic Facilities of a Virtio Device / Feature Bits}
940947
and
941948
\ref{devicenormative:Basic Facilities of a Virtio Device / Feature Bits} for

introduction.tex

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ \chapter{Introduction}
2020
\item[Standard:] Virtio makes no assumptions about the environment in which
2121
it operates, beyond supporting the bus to which device is attached.
2222
In this specification, virtio
23-
devices are implemented over MMIO, Channel I/O and PCI bus transports
23+
devices are implemented over MMIO, Channel I/O, PCI bus, and message-based transports
2424
\footnote{The Linux implementation further separates the virtio
2525
transport code from the specific virtio drivers: these drivers are shared
2626
between different transports.

0 commit comments

Comments
 (0)