summaryrefslogtreecommitdiffstats
path: root/include/migration/vmstate.h
diff options
context:
space:
mode:
authorLaszlo Ersek2018-02-07 13:10:27 +0100
committerMichael S. Tsirkin2018-02-08 20:06:41 +0100
commited247f40db84c8bd4bb7d10948702cd47cc4d5ae (patch)
tree3e398ef67300674d241f722a14def4a08042072d /include/migration/vmstate.h
parentvhost: Move log_dirty check (diff)
downloadqemu-ed247f40db84c8bd4bb7d10948702cd47cc4d5ae.tar.gz
qemu-ed247f40db84c8bd4bb7d10948702cd47cc4d5ae.tar.xz
qemu-ed247f40db84c8bd4bb7d10948702cd47cc4d5ae.zip
pci-bridge/i82801b11: clear bridge registers on platform reset
The "i82801b11-bridge" device model is a descendant of "base-pci-bridge" (TYPE_PCI_BRIDGE). However, unlike other similar devices, such as - pci-bridge, - pcie-pci-bridge, - PCIE Root Port, - xio3130 switch upstream and downstream ports, - dec-21154-p2p-bridge, - pbm-bridge, - xilinx-pcie-root, "i82801b11-bridge" does not clear the bridge specific registers at platform reset. This is a problem because devices on "i82801b11-bridge" continue to respond to config space cycles after platform reset, when addressed with the bus number that was previously programmed into the secondary bus number register of "i82801b11-bridge". This error breaks OVMF's search for extra (PXB) root buses, for example. The device class reset method for "i82801b11-bridge" is currently NULL; set it directly to pci_bridge_reset(), like the last three bridge models in the above listing do. Cc: "Michael S. Tsirkin" <mst@redhat.com> Cc: Marcel Apfelbaum <marcel@redhat.com> Cc: qemu-stable@nongnu.org Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1541839 Signed-off-by: Laszlo Ersek <lersek@redhat.com> Reviewed-by: Marcel Apfelbaum <marcel@redhat.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'include/migration/vmstate.h')
0 files changed, 0 insertions, 0 deletions