| commit | 3385e8e2640e5c38582f6e8413042bd23d97c640 | |
| author | Igor Mammedov <imammedo@redhat.com> | |
| Mon, 7 Sep 2015 11:55:31 +0000 (7 13:55 +0200) | ||
| committer | Michael S. Tsirkin <mst@redhat.com> | |
| Thu, 10 Sep 2015 09:15:30 +0000 (10 12:15 +0300) | ||
| tree | 8fbff6aed49a72d314de70373348ff3b51f5e92e | treesnapshot (tar.gz zip) |
| parent | 9372e3f5678cdd86e1ddfb957d9da4b1889a0dd0 | commitdiff |
pc: memhotplug: fix incorrectly set reserved-memory-end
reserved-memory-end tells firmware address from which
it could start treating memory as PCI address space
and map PCI BARs after it to avoid collisions with
RAM.
Currently it is incorrectly pointing to address where
hotplugged memory range starts which could redirect
hotplugged RAM accesses to PCI BARs when firmware
maps them over RAM or viceverse.
Fix this by pointing reserved-memory-end to the end
of memory hotplug area.
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
reserved-memory-end tells firmware address from which
it could start treating memory as PCI address space
and map PCI BARs after it to avoid collisions with
RAM.
Currently it is incorrectly pointing to address where
hotplugged memory range starts which could redirect
hotplugged RAM accesses to PCI BARs when firmware
maps them over RAM or viceverse.
Fix this by pointing reserved-memory-end to the end
of memory hotplug area.
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
| hw/i386/pc.c | diffblobblamehistory |