virtio — archive

[PATCH v3 0/6] rework notifications terminology

From: Halil Pasic <[email protected]>
To: [email protected]
Date: Mon, 25 Jun 2018 12:22:00 -0000

The various notifications are introduced and specified in the common (i.e. transport agnostic) portion of this specification. How notifications are realised for a given transport is something each transport has to specify. Let's make the relationship between the virtio-ccw terms and the common terms more obvious. Signed-off-by: Halil Pasic <[email protected]> Reviewed-by: Stefan Hajnoczi <[email protected]> Reviewed-by: Cornelia Huck <[email protected]> --- content.tex 42 ++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 42 insertions(+), 0 deletions(-) diff --git a/content.tex b/content.tex index 15d9513..b4e8860 100644 --- a/content.tex +++ b/content.tex @@ -1943,6 +1943,18 @@ Bytes & Description & Contents \ hline end{tabular} +A virtio-ccw proxy device facilitates: +egin{itemize} +item Discovery and attachment of virtio devices (as described above). +item Initialization of virtqueues and transport-specific facilities (using + virtio-specific channel commands). +item Notifications (via hypercall and a combination of I/O interrupts + and indicator bits). +end{itemize} + +subsubsection{Channel Commands for Virtio}label{sec:Virtio Transport Options / Virtio +over channel I/O / Basic Concepts/ Channel Commands for Virtio} + In addition to the basic channel commands, virtio-ccw defines a set of channel commands related to configuration and operation of virtio: @@ -1963,6 +1975,36 @@ virtio: #define CCW_CMD_READ_STATUS 0x72 end{lstlisting} +subsubsection{Notifications}label{sec:Virtio Transport Options / Virtio +over channel I/O / Basic Concepts/ Notifications} + +Available buffer notifications are realized as a hypercall. No additional +setup by the driver is needed. The operation of available buffer +notifications is described in section ef{sec:Virtio Transport Options / +Virtio over channel I/O / Device Operation / Guest->Host Notification}. + +Used buffer notifications are realized either as so-called classic or +adapter I/O interrupts depending on a transport level negotiation. The +initialization is described in sections ef{sec:Virtio Transport Options +/ Virtio over channel I/O / Device Initialization / Setting Up Indicators +/ Setting Up Classic Queue Indicators} and ef{sec:Virtio Transport +Options / Virtio over channel I/O / Device Initialization / Setting Up +Indicators / Setting Up Two-Stage Queue Indicators} respectively. The +operation of each flavor is described in sections ef{sec:Virtio +Transport Options / Virtio over channel I/O / Device Operation / +Host->Guest Notification / Notification via Classic I/O Interrupts} and + ef{sec:Virtio Transport Options / Virtio over channel I/O / Device +Operation / Host->Guest Notification / Notification via Adapter I/O +Interrupts} respectively. + +Configuration change notifications are done using so-called classic I/O +interrupts. The initialization is described in section ef{sec:Virtio +Transport Options / Virtio over channel I/O / Device Initialization / +Setting Up Indicators / Setting Up Configuration Change Indicators} and +the operation in section ef{sec:Virtio Transport Options / Virtio over +channel I/O / Device Operation / Host->Guest Notification / Notification +via Classic I/O Interrupts}. + devicenormative{subsubsection}{Basic Concepts}{Virtio Transport Options / Virtio over channel I/O / Basic Concepts} The virtio-ccw device acts like a normal channel device, as specified -- 1.7.1