summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorMarkus Armbruster2016-06-15 19:56:30 +0200
committerMichael S. Tsirkin2016-07-04 13:50:59 +0200
commit97a83ec3a9d83f2e86b8b93178d8e8b64ccc7486 (patch)
tree8f7d00bfabb8144921601e2a32223fa259c17945 /include
parentmachine: remove iommu property (diff)
downloadqemu-97a83ec3a9d83f2e86b8b93178d8e8b64ccc7486.tar.gz
qemu-97a83ec3a9d83f2e86b8b93178d8e8b64ccc7486.tar.xz
qemu-97a83ec3a9d83f2e86b8b93178d8e8b64ccc7486.zip
piix: Set I440FXState member pci_info.w32 in one place
Range pci_info.w32 records the location of the PCI hole. It's initialized to empty when QOM zeroes I440FXState. That's a fine value for a still unknown PCI hole. i440fx_init() sets pci_info.w32.begin = below_4g_mem_size. Changes the PCI hole from empty to [below_4g_mem_size, UINT64_MAX]. That's a bogus value. i440fx_pcihost_initfn() sets pci_info.end = IO_APIC_DEFAULT_ADDRESS. Since i440fx_init() ran already, this changes the PCI hole to [below_4g_mem_size, IO_APIC_DEFAULT_ADDRESS-1]. That's the correct value. Setting the bounds of the PCI hole in two separate places is confusing, and begs the question whether the bogus intermediate value could be used by something, or what would happen if we somehow managed to realize an i440FX device without having run the board init function i440fx_init() first. Avoid the confusion by setting the (constant) upper bound along with the lower bound in i440fx_init(). Signed-off-by: Markus Armbruster <armbru@redhat.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Reviewed-by: Marcel Apfelbaum <marcel@redhat.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions