[PATCH 11/11] content: Introduce device-specific notifications for MMIO

[Nikos Dragazis <ndragazis@arrikto.com>]

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

diff --git a/content.tex b/content.tex
index d141e92..b0949f9 100644
--- a/content.tex
+++ b/content.tex
@@ -1872,6 +1872,10 @@ \subsection{MMIO Device Register Layout}\label{sec:Virtio Transport Options / Vi
         in at least one of the active virtual queues.
       \item [Configuration Change Notification] - bit 1 - the interrupt was
         asserted because the configuration of the device has changed.
+      \item [Device-specific Notification] - bit 2 - the interrupt was
+        asserted because a device-specific event
+	\ref{sec:Basic Facilities of a Virtio Device / Notifications}
+	occurred.
     \end{description}
   }
   \hline 
@@ -2100,8 +2104,9 @@ \subsubsection{Notifications From The Device}\label{sec:Virtio Transport Options
 The memory mapped virtio device is using a single, dedicated
 interrupt signal, which is asserted when at least one of the
 bits described in the description of \field{InterruptStatus}
-is set. This is how the device sends a used buffer notification
-or a configuration change notification to the device.
+is set. This is how the device sends a
+used buffer/configuration change/device-specific notification to the
+device.
 
 \drivernormative{\paragraph}{Notifications From The Device}{Virtio Transport Options / Virtio Over MMIO / MMIO-specific Initialization And Device Operation / Notifications From The Device}
 After receiving an interrupt, the driver MUST read
-- 
2.17.1