[PATCH 08/11] notifications: Introduce device-specific notifications

[Nikos Dragazis <ndragazis@arrikto.com>]

Signed-off-by: Nikos Dragazis <ndragazis@arrikto.com>
---
 content.tex | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/content.tex b/content.tex
index d6fc17e..661ebd9 100644
--- a/content.tex
+++ b/content.tex
@@ -165,11 +165,12 @@ \section{Notifications}\label{sec:Basic Facilities of a Virtio Device
 to driver) plays an important role in this specification. The
 modus operandi of the notifications is transport specific.
 
-There are three types of notifications: 
+There are four types of notifications:
 \begin{itemize}
 \item configuration change notification
 \item available buffer notification
-\item used buffer notification. 
+\item used buffer notification
+\item device-specific notification.
 \end{itemize}
 
 Configuration change notifications and used buffer notifications are sent
@@ -182,6 +183,11 @@ \section{Notifications}\label{sec:Basic Facilities of a Virtio Device
 the device. This type of notification indicates that a buffer may have
 been made available on the virtqueue designated by the notification.
 
+Device-specific notifications are sent by the device, the recipient is
+the driver. Their purpose is to allow the device to send notifications
+other than configuration changes and used buffer notifications. These
+notifications are optional and their meaning is device-specific.
+
 The semantics, the transport-specific implementations, and other
 important aspects of the different notifications are specified in detail
 in the following chapters.
-- 
2.17.1