Adding relevant registers needs more work and it's not clear what the use-case will be as currently only the PCI transport is supported. But let's keep the door open on this. We already say it's reserved in a central place, but it does not hurt to remind implementers to mask it.
Signed-off-by: Michael S. Tsirkin <[email protected]> Reviewed-by: Parav Pandit <[email protected]> Reviewed-by: Stefan Hajnoczi <[email protected]> Reviewed-by: Max Gurtovoy <[email protected]> --- changes in v12: drop "as of now" to address comment by parav --- transport-mmio.tex | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/transport-mmio.tex b/transport-mmio.tex index f884a2c..5680fc4 100644 --- a/transport-mmio.tex +++ b/transport-mmio.tex @@ -562,3 +562,15 @@ \subsection{Legacy interface}\label{sec:Virtio Transport Options / Virtio Over M \end{enumerate} Notification mechanisms did not change. + +\subsection{Features reserved for future use}\label{sec:Virtio Transport Options / Virtio Over MMIO / Features reserved for future use} + +Devices and drivers utilizing Virtio Over MMIO +do not support the following features: +\begin{itemize} + +\item VIRTIO_F_ADMIN_VQ + +\end{itemize} + +These features are reserved for future use. -- MST --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
