Hello, Quick update about this work:
- the hotunplug timeout was reverted in the pSeries machine for 6.0.0. This means that we have no use for a DEVICE_NOT_DELETED event or similar. I'll drop it for the next version of the series. - there is a good chance that the pSeries kernel will introduce a way to report hotunplug errors in v5.13 ([1] for more info). This would make the DEVICE_UNPLUG_ERROR event relevant again (otherwise it would just be a rebranding of the existing mem_unplug_error) since we'll be able to properly report guest side unplug errors for all devices in the pSeries machine, starting with CPUs. Thanks, DHB [1] https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20210416210216.380291-3-danielhb...@gmail.com/ On 3/12/21 5:07 PM, Daniel Henrique Barboza wrote:
Hi, This series adds 2 new QAPI events, DEVICE_NOT_DELETED and DEVICE_UNPLUG_ERROR. They were (and are still being) discussed in [1]. Patches 1 and 3 are independent of the ppc patches and can be applied separately. Patches 2 and 4 are based on David's ppc-for-6.0 branch and are dependent on the QAPI patches. [1] https://lists.gnu.org/archive/html/qemu-devel/2021-03/msg01900.html Daniel Henrique Barboza (4): qapi/qdev.json: add DEVICE_NOT_DELETED event spapr_drc.c: send DEVICE_NOT_DELETED event on unplug timeout qapi/machine.json: add DEVICE_UNPLUG_ERROR QAPI event spapr.c: use DEVICE_UNPLUG_ERROR event in spapr_memory_unplug_rollback() hw/ppc/spapr.c | 2 +- hw/ppc/spapr_drc.c | 8 ++++++++ qapi/machine.json | 23 +++++++++++++++++++++++ qapi/qdev.json | 28 ++++++++++++++++++++++++++++ 4 files changed, 60 insertions(+), 1 deletion(-)