From e94ddeac0605ab0f4b45ef62a392c2eed5020330 Mon Sep 17 00:00:00 2001 From: Boris Fiuczynski Date: Fri, 17 Apr 2020 14:27:34 +0200 Subject: [PATCH] docs: Improve zPCI section in pci-addresses.rst Improving the zPCI example by choosing more distinct values and adding explanation for fid. Signed-off-by: Boris Fiuczynski Reviewed-by: Cornelia Huck Reviewed-by: Andrea Bolognani --- docs/pci-addresses.rst | 22 ++++++++++++---------- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/docs/pci-addresses.rst b/docs/pci-addresses.rst index 7c8e9edd73..885d50517a 100644 --- a/docs/pci-addresses.rst +++ b/docs/pci-addresses.rst @@ -176,14 +176,14 @@ In the simplest case, the following XML snippet
- +
- +
@@ -191,21 +191,23 @@ will result in the following in a Linux guest: :: - 0001:00:00.0 Ethernet controller: Red Hat, Inc. Virtio network device + 0007:00:00.0 Ethernet controller: Red Hat, Inc. Virtio network device Note that the PCI bridge is not visible in the guest; s390x always has a flat -topology. +topology. The PCI address in the guest is generated from the information +provided via the ``zpci`` element: more specifically, ``uid`` is used as the +PCI domain. ``fid`` doesn't appear in the PCI address itself, but it will be +used in sysfs (``/sys/bus/pci/slots/$fid/...``). -Neither are any changes in the PCI address visible in the guest; replacing -the PCI address for the ``virtio-net`` device with +Any changes in the PCI address are not visible in the guest; replacing the PCI +address for the ``virtio-net`` device with :: -
+
-will result in the exactly same view in the guest, as the addresses there -are generated from the information provided via the ``zpci`` element (in -fact, from the ``uid``). +will result in the exactly same view in the guest, as the ``fid`` and ``uid`` +values in the ``zpci`` element remain unchanged. Device assignment -- GitLab