Thomas Huth bc9da794cc hw/s390x: Re-enable the pci-bridge device on s390x ... Commit e779e5c05a ("hw/pci-bridge: Add a Kconfig switch for the normal PCI bridge") added a config switch for the pci-bridge, so that the device is not included in the s390x target anymore (since the pci-bridge is not really useful on s390x). However, it seems like libvirt is still adding pci-bridge devices automatically to the guests' XML definitions (when adding a PCI device to a non-zero PCI bus), so these guests are now broken due to the missing pci-bridge in the QEMU binary. To avoid disruption of the users, let's re-enable the pci-bridge device on s390x for the time being. Message-ID: <20241024130405.62134-1-thuth@redhat.com> Reviewed-by: Cédric Le Goater <clg@redhat.com> Reviewed-by: Boris Fiuczynski <fiuczy@linux.ibm.com> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org> Signed-off-by: Thomas Huth <thuth@redhat.com>		2024-11-04 14:16:11 +01:00
..
3270-ccw.c
ap-bridge.c
ap-device.c
ccw-device.c
ccw-device.h
cpu-topology.c
css-bridge.c
css.c
event-facility.c
ipl.c
ipl.h
Kconfig	hw/s390x: Re-enable the pci-bridge device on s390x	2024-11-04 14:16:11 +01:00
meson.build
s390-ccw.c
s390-pci-bus.c
s390-pci-inst.c
s390-pci-kvm.c
s390-pci-vfio.c
s390-skeys-kvm.c
s390-skeys.c
s390-stattrib-kvm.c
s390-stattrib.c
s390-virtio-ccw.c
s390-virtio-hcall.c
s390-virtio-hcall.h
sclp.c
sclpcpu.c
sclpquiesce.c
tod-kvm.c
tod-tcg.c
tod.c
trace-events
trace.h
vhost-scsi-ccw.c
vhost-user-fs-ccw.c
vhost-vsock-ccw.c
virtio-ccw-9p.c
virtio-ccw-balloon.c
virtio-ccw-blk.c
virtio-ccw-crypto.c
virtio-ccw-gpu.c
virtio-ccw-input.c
virtio-ccw-net.c
virtio-ccw-rng.c
virtio-ccw-scsi.c
virtio-ccw-serial.c
virtio-ccw.c
virtio-ccw.h