diff options
| -rw-r--r-- | conformance.tex | 1 | ||||
| -rw-r--r-- | content.tex | 2 | ||||
| -rw-r--r-- | shared-mem.tex | 42 |
3 files changed, 45 insertions, 0 deletions
diff --git a/conformance.tex b/conformance.tex index 42f702a..4524237 100644 --- a/conformance.tex +++ b/conformance.tex @@ -197,6 +197,7 @@ A device MUST conform to the following normative statements: \item \ref{devicenormative:Basic Facilities of a Virtio Device / Virtqueues / Used Buffer Notification Suppression} \item \ref{devicenormative:Basic Facilities of a Virtio Device / Virtqueues / The Virtqueue Used Ring} \item \ref{devicenormative:Basic Facilities of a Virtio Device / Virtqueues / Available Buffer Notification Suppression} +\item \ref{devicenormative:Basic Facilities of a Virtio Device / Shared Memory Regions} \item \ref{devicenormative:Reserved Feature Bits} \end{itemize} diff --git a/content.tex b/content.tex index 8f0498e..6433226 100644 --- a/content.tex +++ b/content.tex @@ -371,6 +371,8 @@ making any more buffers available. When VIRTIO_F_NOTIFICATION_DATA has been negotiated, these notifications would then have identical \field{next_off} and \field{next_wrap} values. +\input{shared-mem.tex} + \chapter{General Initialization And Device Operation}\label{sec:General Initialization And Device Operation} We start with an overview of device initialization, then expand on the diff --git a/shared-mem.tex b/shared-mem.tex new file mode 100644 index 0000000..6e6f6c4 --- /dev/null +++ b/shared-mem.tex @@ -0,0 +1,42 @@ +\section{Shared Memory Regions}\label{sec:Basic Facilities of a Virtio Device / Shared Memory Regions} + +Shared memory regions are an additional facility +available to devices that need a region of memory that's +continuously shared between the device and the driver, rather +than passed between them in the way virtqueue elements are. + +Example uses include shared caches and version pools for versioned +data structures. + +The memory region is allocated by the device and presented to the +driver. Where the device is implemented in software on a host, +this arrangement allows the memory region to be allocated by +a library on the host, which the device may not have full control +over. + +A device may have multiple shared memory regions associated with +it. Each region has a \field{shmid} to identify it, the meaning +of which is device-specific. + +Enumeration and location of shared memory regions is performed +in a transport-specific way. + +Memory consistency rules vary depending on the region and the +device and they will be specified as required by each device. + +\subsection{Addressing within regions}\label{sec:Basic Facilities of a Virtio Device / Shared Memory Regions / Addressing within regions } + +References into shared memory regions are represented as offsets from +the beginning of the region instead of absolute memory addresses. +Offsets are used both for references between structures stored +within shared memory and for requests placed in virtqueues that +refer to shared memory. +The \field{shmid} may be explicit or may be inferred from the +context of the reference. + +\devicenormative{\subsection}{Shared Memory Regions}{Basic Facilities of a Virtio +Device / Shared Memory Regions} +Shared memory regions MUST NOT expose shared memory regions which +are used to control the operation of the device, nor to stream +data. + |