[PATCH 4/6] admin: Reference transport specific administration virtqueue discovery

[Parav Pandit <parav@nvidia.com>]

The administration virtqueues section states that the number and
locations of administration virtqueues are exposed in a transport
specific manner, without pointing to where this is described.

Now that both the PCI and the MMIO transports describe it, add
references to the respective transport sections.

Signed-off-by: Parav Pandit <parav@nvidia.com>
---
 admin.tex | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/admin.tex b/admin.tex
index cfca5e3..a639c17 100644
--- a/admin.tex
+++ b/admin.tex
@@ -493,7 +493,11 @@ \section{Administration Virtqueues}\label{sec:Basic Facilities of a Virtio Devic
 If VIRTIO_F_ADMIN_VQ has been negotiated, an owner device exposes one
 or more administration virtqueues. The number and locations of the
 administration virtqueues are exposed by the owner device in a transport
-specific manner.
+specific manner, see
+\ref{sec:Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Common configuration structure layout}~\nameref{sec:Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Common configuration structure layout}
+for the PCI transport and
+\ref{sec:Virtio Transport Options / Virtio Over MMIO / MMIO-specific Initialization And Device Operation / Administration Virtqueues}~\nameref{sec:Virtio Transport Options / Virtio Over MMIO / MMIO-specific Initialization And Device Operation / Administration Virtqueues}
+for the MMIO transport.
 
 The driver enqueues requests to an arbitrary administration
 virtqueue, and they are used by the device on that same
-- 
2.43.0