Skip to content

Commit 92a39c6

Browse files
virtio-msg: create a Device discovery section
Create a stand-alone device discovery section to have the same organization as other transports. Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>
1 parent 1a617c7 commit 92a39c6

1 file changed

Lines changed: 15 additions & 11 deletions

File tree

transport-msg.tex

Lines changed: 15 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -376,18 +376,12 @@ \subsubsection{Message Correlation}
376376
action.
377377
\end{itemize}
378378

379-
\subsection{Bus Operation}
380-
\label{sec:Virtio Transport Options / Virtio Over Messages / Bus Operation}
381-
382-
A \textbf{virtio-msg bus} is responsible for identifying available virtio devices
383-
and informing the operating system (or higher-level software environment) so
384-
that those devices can be bound to the appropriate driver. The following
385-
subsections describe optional messaging mechanisms that a bus MAY use to
386-
discover or manage devices, as well as general guidelines for completing the
387-
device registration process.
379+
\subsection{Device Discovery}\label{sec:Virtio Transport Options / Virtio Over Messages / Device Discovery}
388380

389-
\subsubsection{Device Discovery}
390-
\label{sec:Virtio Transport Options / Virtio Over Messages / Bus Operation / Device Discovery}
381+
A virtio-msg implementation can learn about devices via bus-level enumeration
382+
(e.g., \busref{GET_DEVICES}), platform data (e.g., device tree, ACPI), or
383+
hypervisor/firmware interfaces. The following informative text describes
384+
typical flows; the normative obligations follow.
391385

392386
Bus implementations MAY discover their devices in various ways:
393387
\begin{itemize}
@@ -406,6 +400,16 @@ \subsubsection{Device Discovery}
406400
and vendor ID. The bus can then register the device with the host OS
407401
so the appropriate virtio driver probe routine is invoked.
408402

403+
\subsection{Bus Operation}
404+
\label{sec:Virtio Transport Options / Virtio Over Messages / Bus Operation}
405+
406+
A \textbf{virtio-msg bus} is responsible for identifying available virtio devices
407+
and informing the operating system (or higher-level software environment) so
408+
that those devices can be bound to the appropriate driver. The following
409+
subsections describe optional messaging mechanisms that a bus MAY use to
410+
discover or manage devices, as well as general guidelines for completing the
411+
device registration process.
412+
409413
\subsubsection{Device Hotplug}
410414
\label{sec:Virtio Transport Options / Virtio Over Messages / Bus Operation / Device Hotplug}
411415

0 commit comments

Comments
 (0)