Update 'Device address' section to describe 'zpci' element and
its two attributes 'uid' and 'fid'.
Signed-off-by: Yi Min Zhao <zyimin(a)linux.ibm.com>
Reviewed-by: Boris Fiuczynski <fiuczy(a)linux.ibm.com>
Reviewed-by: Stefan Zimmermann <stzi(a)linux.ibm.com>
Reviewed-by: Ján Tomko <jtomko(a)redhat.com>
Reviewed-by: Andrea Bolognani <abologna(a)redhat.com>
---
docs/formatdomain.html.in | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in
index 269741a690..dd89a95c3c 100644
--- a/docs/formatdomain.html.in
+++ b/docs/formatdomain.html.in
@@ -3925,7 +3925,15 @@
(<span class="since">since 0.9.7, requires QEMU
0.13</span>). <code>multifunction</code> defaults to
'off',
but should be set to 'on' for function 0 of a slot that will
- have multiple functions used.<br/>
+ have multiple functions used.
+ (<span class="since">Since 4.10.0</span>), PCI address
extensions
+ depending on the architecture are supported. For example, PCI
+ addresses for S390 guests will have a <code>zpci</code> child
+ element, with two attributes: <code>uid</code> (a hex value
+ between 0x0001 and 0xffff, inclusive), and <code>fid</code> (a
+ hex value between 0x00000000 and 0xffffffff, inclusive) used by
+ PCI devices on S390 for User-defined Identifiers and Function
+ Identifiers.<br/>
<span class="since">Since 1.3.5</span>, some hypervisor
drivers may accept an <code><address
type='pci'/></code>
element with no other attributes as an explicit request to
--
Yi Min