External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-07-31 14:07:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: drvnodedev: Fix local anchor links

Browse Source 
Original conversion didn't properly convert local links. Fix them by
pointing to the section name. In certain cases this requires
reformulation of the text.

Signed-off-by: Peter Krempa <pkrempa@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
This commit is contained in:
Peter Krempa 2022-04-13 15:27:49 +02:00
parent a070fecbf8
commit 6d9ae27f62
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/drvnodedev.rst
View File

@ -59,8 +59,7 @@ PCI host devices
``capability`` ``capability``
When used as top level element, the supported values for the ``type`` When used as top level element, the supported values for the ``type``
attribute are ``pci`` and ``phys_function`` (see `SR-IOV attribute are ``pci`` and ``phys_function`` (see `SR-IOV capability`_ below).
below <#SRIOVCap>`__).
:: ::
@ -103,9 +102,10 @@ multiple devices called virtual functions (VFs) sharing their configuration with
the underlying PF. Despite the SR-IOV specification, the amount of VFs that can the underlying PF. Despite the SR-IOV specification, the amount of VFs that can
be created on a PF varies among manufacturers. be created on a PF varies among manufacturers.
Suppose the NIC `above <#PCI>`__ was also SR-IOV capable, it would also include Suppose the NIC above in `PCI host devices`_ was also SR-IOV capable, it would
a nested ``<capability>`` element enumerating all virtual functions available on also include a nested ``<capability>`` element enumerating all virtual
the physical device (physical port) like in the example below. functions available on the physical device (physical port) like in the example
below.
:: ::
@ -146,8 +146,8 @@ of the XML format for the ``mdev_types`` capability can be found
`here <formatnode.html#MDEVTypesCap>`__. `here <formatnode.html#MDEVTypesCap>`__.
The following example shows how we might represent an NVIDIA GPU device that The following example shows how we might represent an NVIDIA GPU device that
supports mediated devices. See below for `more information about mediated supports mediated devices. See below for more info on
devices <#MDEV>`__. `Mediated devices (MDEVs)`_.
:: ::
@ -281,7 +281,7 @@ covers the following features:
Because mediated devices are instantiated from vendor specific templates, simply Because mediated devices are instantiated from vendor specific templates, simply
called 'types', information describing these types is contained within the called 'types', information describing these types is contained within the
parent device's capabilities (see the example in `PCI host devices <#PCI>`__). parent device's capabilities (see the example in `PCI host devices`_).
To list all devices capable of creating mediated devices, the following command To list all devices capable of creating mediated devices, the following command
can be used. can be used.