We're going to use the 'targetIndex' element for PowerNV PHBs. Clarify
that the same attribute will have a different meaning in this context.

Signed-off-by: Daniel Henrique Barboza <danielhb...@gmail.com>
---
 docs/formatdomain.rst | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst
index 4693c22707..e941e8e892 100644
--- a/docs/formatdomain.rst
+++ b/docs/formatdomain.rst
@@ -3895,8 +3895,10 @@ generated by libvirt. :since:`Since 1.2.19 (QEMU only).`
    the user of the libvirt API to attach host devices to the correct
    pci-expander-bus when assigning them to the domain).
 ``index``
-   pci-root controllers for pSeries guests use this attribute to record the
-   order they will show up in the guest. :since:`Since 3.6.0`
+   pci-root controllers for ``pSeries`` guests use this attribute to record the
+   order they will show up in the guest (:since:`Since 3.6.0`). :since:`Since 
8.1.0`,
+   ``powernv`` domains uses this attribute to indicate which slot inside the
+   chip the pcie-root controller will use.
 ``chip-id``
    pcie-root controllers for ``powernv`` domains use this attribute to indicate
    the chip that will own the controller. A chip is equivalent to a CPU socket.
-- 
2.35.1

Reply via email to