v1->v2:
Suggested by Peter Maydell, rename events to make them
architecture-neutral:
'PC-RAM' -> 'guest-memory'
'guest-triple-fault' -> 'guest-mce-fatal'
Suggested by Paolo, add more fields in event:
'action-required': boolean type to distinguish a guest-mce is AR/AO.
'recursive': boolean type. set true if: previous MCE in processing
in guest, another AO MCE occurs.
v1:
Although QEMU could catch signal BUS to handle hardware memory
corrupted event, sadly, QEMU just prints a little log and try to fix
it silently.
In these patches, introduce a 'MEMORY_FAILURE' event with 4 detailed
actions of QEMU, then uplayer could know what situaction QEMU hit and
did. And further step we can do: if a host server hits a 'hypervisor-ignore'
or 'guest-mce', scheduler could migrate VM to another host; if hitting
'hypervisor-stop' or 'guest-triple-fault', scheduler could select other
healthy servers to launch VM.
Zhenwei Pi (3):
target-i386: seperate MCIP & MCE_MASK error reason
qapi/run-state.json: introduce memory failure event
target-i386: post memory failure event to uplayer
qapi/run-state.json | 67 ++++++++++++++++++++++++++++++++++++++++++++++++++++
target/i386/helper.c | 40 +++++++++++++++++++++++++------
target/i386/kvm.c | 7 +++++-
3 files changed, 106 insertions(+), 8 deletions(-)