On Wed, Jul 31, 2019 at 10:32:18AM +0200, Michal Privoznik wrote:
>As reported here [1], a PCI domain can be just any number. Well, not in
>case of traditional 32-bit PCI, bit in case of PCI-X (64-bit PCI; not to
>be confused with PCI Express), the PCI domain number can really be just
>anything. I wanted to download the specification from PCI SIG web but
>it's paid (why on earth would somebody create a standard and then make
>it not widely available is beyond me).
>
>1: https://www.redhat.com/archives/libvir-list/2019-July/msg01732.html
>
>Michal Prívozník (6):
> qemuBuildPCIHostdevDevStr: Always format PCI domain onto cmd line
> virPCIDeviceNew: Prefer VIR_RETURN_PTR
> virPCIDevice: Make @name dynamically allocated
> lib: Unify PCI address formatting
> lib: Format PCI address differently
> virpci: Allow greater PCI domain value in virPCIDeviceAddressIsValid
>
> docs/schemas/basictypes.rng | 2 +-
> src/conf/device_conf.c | 4 +-
> src/conf/domain_addr.c | 10 ++--
> src/conf/domain_audit.c | 3 +-
> src/conf/domain_conf.c | 12 ++---
> src/conf/node_device_conf.c | 12 ++---
> src/libxl/libxl_driver.c | 14 +++--
> src/qemu/qemu_command.c | 9 ++--
> src/qemu/qemu_hotplug.c | 5 +-
> src/util/virpci.c | 52 +++++++++----------
> src/util/virpci.h | 2 +
> .../hostdev-pci-address-device.args | 2 +-
> .../qemuxml2argvdata/hostdev-pci-address.args | 2 +-
> .../hostdev-vfio-zpci-autogenerate.args | 2 +-
> .../hostdev-vfio-zpci-boundaries.args | 2 +-
> tests/qemuxml2argvdata/hostdev-vfio-zpci.args | 2 +-
> tests/qemuxml2argvdata/hostdev-vfio.args | 2 +-
> .../net-hostdev-bootorder.args | 3 +-
> tests/qemuxml2argvdata/net-hostdev-vfio.args | 2 +-
> tests/qemuxml2argvdata/net-hostdev.args | 2 +-
> tests/qemuxml2argvdata/pci-domain-invalid.xml | 2 +-
> tests/qemuxml2argvdata/pci-rom.args | 4 +-
> tools/virsh-domain.c | 4 +-
> 23 files changed, 81 insertions(+), 73 deletions(-)
>
Reviewed-by: Ján Tomko <jtomko@redhat.com>
Jano
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list