ich777/linux_media
1
0
Fork 0
mirror of https://github.com/tbsdtv/linux_media.git synced 2025-07-23 20:51:03 +02:00
Code Issues Packages Projects Releases Wiki Activity

s390/docs: fix warnings for vfio_ap driver doc

Browse Source 
Fix multiple warnings produced by make htmldocs

Fixes: cb269e0aba ("s390/vfio-ap: update docs to include dynamic config support")
Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>
This commit is contained in:
Alexander Gordeev
2022-07-21 15:59:36 +02:00
parent d384690c6a
commit 9aa938ddce
1 changed files with 9 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
Documentation/s390/vfio-ap.rst
View File

@@ -681,7 +681,7 @@ These are the steps:
default drivers pool: adapter 0-15, domain 1 default drivers pool: adapter 0-15, domain 1
alternate drivers pool: adapter 16-255, domains 0, 2-255 alternate drivers pool: adapter 16-255, domains 0, 2-255
Note ***: **Note:**
Changing a mask such that one or more APQNs will be taken from a vfio_ap Changing a mask such that one or more APQNs will be taken from a vfio_ap
mediated device (see below) will fail with an error (EBUSY). A message mediated device (see below) will fail with an error (EBUSY). A message
is logged to the kernel ring buffer which can be viewed with the 'dmesg' is logged to the kernel ring buffer which can be viewed with the 'dmesg'
@@ -940,7 +940,7 @@ host. If the vfio_ap mdev is removed, one may want to also reconfigure
the pool of adapters and queues reserved for use by the default drivers. the pool of adapters and queues reserved for use by the default drivers.
Hot plug/unplug support: Hot plug/unplug support:
================ ========================
An adapter, domain or control domain may be hot plugged into a running KVM An adapter, domain or control domain may be hot plugged into a running KVM
guest by assigning it to the vfio_ap mediated device being used by the guest if guest by assigning it to the vfio_ap mediated device being used by the guest if
the following conditions are met: the following conditions are met:
@@ -962,7 +962,7 @@ guest by unassigning it from the vfio_ap mediated device being used by the
guest. guest.
Over-provisioning of AP queues for a KVM guest: Over-provisioning of AP queues for a KVM guest:
============================================== ===============================================
Over-provisioning is defined herein as the assignment of adapters or domains to Over-provisioning is defined herein as the assignment of adapters or domains to
a vfio_ap mediated device that do not reference AP devices in the host's AP a vfio_ap mediated device that do not reference AP devices in the host's AP
configuration. The idea here is that when the adapter or domain becomes configuration. The idea here is that when the adapter or domain becomes
@@ -992,6 +992,8 @@ its mdev can be hot unplugged from the guest in one of two ways:
The contents of my-guest-hostdev.xml: The contents of my-guest-hostdev.xml:
.. code-block:: xml
<hostdev mode='subsystem' type='mdev' managed='no' model='vfio-ap'> <hostdev mode='subsystem' type='mdev' managed='no' model='vfio-ap'>
<source> <source>
<address uuid='62177883-f1bb-47f0-914d-32a22e3a8804'/> <address uuid='62177883-f1bb-47f0-914d-32a22e3a8804'/>
@@ -1004,6 +1006,8 @@ its mdev can be hot unplugged from the guest in one of two ways:
For example, to hot unplug the vfio_ap mediated device identified on the For example, to hot unplug the vfio_ap mediated device identified on the
qemu command line with 'id=hostdev0' from the guest named 'my-guest': qemu command line with 'id=hostdev0' from the guest named 'my-guest':
.. code-block:: sh
virsh qemu-monitor-command my-guest --hmp "device_del hostdev0" virsh qemu-monitor-command my-guest --hmp "device_del hostdev0"
2. A vfio_ap mediated device can be hot unplugged by attaching the qemu monitor 2. A vfio_ap mediated device can be hot unplugged by attaching the qemu monitor
@@ -1032,6 +1036,8 @@ system into the guest in one of two ways:
The contents of my-guest-hostdev.xml: The contents of my-guest-hostdev.xml:
.. code-block:: xml
<hostdev mode='subsystem' type='mdev' managed='no' model='vfio-ap'> <hostdev mode='subsystem' type='mdev' managed='no' model='vfio-ap'>
<source> <source>
<address uuid='62177883-f1bb-47f0-914d-32a22e3a8804'/> <address uuid='62177883-f1bb-47f0-914d-32a22e3a8804'/>