Yuri Benditovich 348e354417 pci: do not respond config requests after PCI device eject ... Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=2224964 In migration with VF failover, Windows guest and ACPI hot unplug we do not need to satisfy config requests, otherwise the guest immediately detects the device and brings up its driver. Many network VF's are stuck on the guest PCI bus after the migration. Signed-off-by: Yuri Benditovich <yuri.benditovich@daynix.com> Message-Id: <20230728084049.191454-1-yuri.benditovich@daynix.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>		2023-08-03 16:06:49 -04:00
..
Kconfig	kconfig: Add PCIe devices to s390x machines	2023-07-14 11:10:57 +02:00
meson.build	meson: Replace softmmu_ss -> system_ss	2023-06-20 10:01:30 +02:00
msi.c
msix.c
pci-hmp-cmds.c
pci-internal.h
pci-qmp-cmds.c
pci-stub.c
pci.c	hw/pci: add comment to explain checking for available function 0 in pci hotplug	2023-07-25 17:19:44 +03:00
pci_bridge.c
pci_host.c	pci: do not respond config requests after PCI device eject	2023-08-03 16:06:49 -04:00
pcie.c	pcie: Specify 0 for ARI next function numbers	2023-07-10 18:59:32 -04:00
pcie_aer.c
pcie_doe.c
pcie_host.c
pcie_port.c
pcie_sriov.c	pcie: Release references of virtual functions	2023-07-10 18:59:32 -04:00
shpc.c
slotid_cap.c
trace-events
trace.h