pci_bridge: use parent bus's address space
The switch to the new memory API caused the following problem: The pci device may call pci_register_bar() to use PCI bus's address space. But we don't init PCI bus's address space if it is not bus 0. A crash was reported: http://lists.gnu.org/archive/html/qemu-devel/2011-08/msg02243.html More work will be needed to make bridge filtering work correctly with the memory API. Signed-off-by: Wen Congyang <wency@cn.fujitsu.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
This commit is contained in:
parent
a92eb87a44
commit
778d179939
@ -246,6 +246,9 @@ int pci_bridge_initfn(PCIDevice *dev)
|
||||
br->bus_name);
|
||||
sec_bus->parent_dev = dev;
|
||||
sec_bus->map_irq = br->map_irq;
|
||||
/* TODO: use memory API to perform memory filtering. */
|
||||
sec_bus->address_space_mem = parent->address_space_mem;
|
||||
sec_bus->address_space_io = parent->address_space_io;
|
||||
|
||||
QLIST_INIT(&sec_bus->child);
|
||||
QLIST_INSERT_HEAD(&parent->child, sec_bus, sibling);
|
||||
|
Loading…
Reference in New Issue
Block a user