diff options
| author | Greg Kurz | 2020-12-14 11:05:50 +0100 |
|---|---|---|
| committer | David Gibson | 2021-01-06 01:09:59 +0100 |
| commit | 1e8b5b1aa16b7d73ba8ba52c95d0b52329d5c9d0 (patch) | |
| tree | 635d0e1e6cd542f1b65b394e4a4af3c1669e8fbc /include/hw/pci-host/spapr.h | |
| parent | spapr: Fix DR properties of the root node (diff) | |
| download | qemu-1e8b5b1aa16b7d73ba8ba52c95d0b52329d5c9d0.tar.gz qemu-1e8b5b1aa16b7d73ba8ba52c95d0b52329d5c9d0.tar.xz qemu-1e8b5b1aa16b7d73ba8ba52c95d0b52329d5c9d0.zip | |
spapr: Allow memory unplug to always succeed
It is currently impossible to hot-unplug a memory device between
machine reset and CAS.
(qemu) device_del dimm1
Error: Memory hot unplug not supported for this guest
This limitation was introduced in order to provide an explicit
error path for older guests that didn't support hot-plug event
sources (and thus memory hot-unplug).
The linux kernel has been supporting these since 4.11. All recent
enough guests are thus capable of handling the removal of a memory
device at all time, including during early boot.
Lift the limitation for the latest machine type. This means that
trying to unplug memory from a guest that doesn't support it will
likely just do nothing and the memory will only get removed at
next reboot. Such older guests can still get the existing behavior
by using an older machine type.
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <160794035064.23292.17560963281911312439.stgit@bahia.lan>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'include/hw/pci-host/spapr.h')
0 files changed, 0 insertions, 0 deletions