NuKVM/libvirt
3
0
Fork 0
mirror of https://github.com/libvirt/libvirt.git synced 2025-02-25 18:55:26 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs: Fix names for PF and VF PCI device capabilities

Browse Source 
The proper name for physical function capability is 'phys_function', not
'physical_function'. Likewise, a virtual function capability is
'virt_functions' rather than 'virtual_function'.

Signed-off-by: Jonathon Jongsma <jjongsma@redhat.com>
Reviewed-by: Erik Skultety <eskultet@redhat.com>
This commit is contained in:
Jonathon Jongsma 2020-05-21 15:09:34 -05:00 committed by Erik Skultety
parent 23d8b99f3e
commit e68c290f4b
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/formatnode.html.in
View File

@ -109,7 +109,7 @@
exists, it has a mandatory <code>type</code> attribute exists, it has a mandatory <code>type</code> attribute
which will be set to: which will be set to:
<dl> <dl>
<dt><code>physical_function</code></dt> <dt><code>phys_function</code></dt>
<dd> <dd>
That means there will be a single <code>address</code> That means there will be a single <code>address</code>
subelement which contains the PCI address of the SRIOV subelement which contains the PCI address of the SRIOV
@ -117,7 +117,7 @@
(and this device is, by implication, an SRIOV Virtual (and this device is, by implication, an SRIOV Virtual
Function (VF)). Function (VF)).
</dd> </dd>
<dt><code>virtual_function</code></dt> <dt><code>virt_functions</code></dt>
<dd> <dd>
In this case this device is an SRIOV PF, and the capability In this case this device is an SRIOV PF, and the capability
element will have a list of <code>address</code> element will have a list of <code>address</code>