diff options
author | Daniel Henrique Barboza | 2021-03-02 15:10:19 +0100 |
---|---|---|
committer | David Gibson | 2021-03-09 23:07:09 +0100 |
commit | eb7f80fd26d73e7e1af105431da58971b1dba517 (patch) | |
tree | 78d653f458a49e9c97f9da28c16b4ec360c130b1 /target/ppc | |
parent | spapr.c: remove duplicated assert in spapr_memory_unplug_request() (diff) | |
download | qemu-eb7f80fd26d73e7e1af105431da58971b1dba517.tar.gz qemu-eb7f80fd26d73e7e1af105431da58971b1dba517.tar.xz qemu-eb7f80fd26d73e7e1af105431da58971b1dba517.zip |
spapr.c: send QAPI event when memory hotunplug fails
Recent changes allowed the pSeries machine to rollback the hotunplug
process for the DIMM when the guest kernel signals, via a
reconfiguration of the DR connector, that it's not going to release the
LMBs.
Let's also warn QAPI listerners about it. One place to do it would be
right after the unplug state is cleaned up,
spapr_clear_pending_dimm_unplug_state(). This would mean that the
function is now doing more than cleaning up the pending dimm state
though.
This patch does the following changes in spapr.c:
- send a QAPI event to inform that we experienced a failure in the
hotunplug of the DIMM;
- rename spapr_clear_pending_dimm_unplug_state() to
spapr_memory_unplug_rollback(). This is a better fit for what the
function is now doing, and it makes callers care more about what the
function goal is and less about spapr.c internals such as clearing
the pending dimm unplug state.
Reviewed-by: Greg Kurz <groug@kaod.org>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20210302141019.153729-3-danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'target/ppc')
0 files changed, 0 insertions, 0 deletions