diff options
| author | Wei Yang <richardw.yang@linux.intel.com> | 2019-03-01 11:35:48 +0800 |
|---|---|---|
| committer | Michael S. Tsirkin <mst@redhat.com> | 2019-03-12 22:31:21 -0400 |
| commit | 9040e6dfa8c3fed87695a3de555d2c775727bb51 (patch) | |
| tree | 29545b706420f8ab2048a2be270665f31d04564d /python | |
| parent | e07fb4b50b629141eb1517002ccfa070dbdc1ea7 (diff) | |
| download | qemu-9040e6dfa8c3fed87695a3de555d2c775727bb51.zip qemu-9040e6dfa8c3fed87695a3de555d2c775727bb51.tar.gz qemu-9040e6dfa8c3fed87695a3de555d2c775727bb51.tar.bz2 | |
i386, acpi: check acpi_memory_hotplug capacity in pre_plug
Currently we do device realization like below:
hotplug_handler_pre_plug()
dc->realize()
hotplug_handler_plug()
Before we do device realization and plug, we should allocate necessary
resources and check if memory-hotplug-support property is enabled.
At the piix4 and ich9, the memory-hotplug-support property is checked at
plug stage. This means that device has been realized and mapped into guest
address space 'pc_dimm_plug()' by the time acpi plug handler is called,
where it might fail and crash QEMU due to reaching g_assert_not_reached()
(piix4) or error_abort (ich9).
Fix it by checking if memory hotplug is enabled at pre_plug stage
where we can gracefully abort hotplug request.
Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
CC: Igor Mammedov <imammedo@redhat.com>
CC: Eric Blake <eblake@redhat.com>
Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
Message-Id: <20190301033548.6691-1-richardw.yang@linux.intel.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'python')
0 files changed, 0 insertions, 0 deletions