From: zhenwei pi <pizhenwei@bytedance.com>
To: armbru@redhat.com, pbonzini@redhat.com, mtosatti@redhat.com
Cc: qemu-devel@nongnu.org, pizhenwei@bytedance.com
Subject: [PATCH 0/3] add MEMORY_FAILURE event
Date: Mon, 14 Sep 2020 21:43:18 +0800 [thread overview]
Message-ID: <20200914134321.958079-1-pizhenwei@bytedance.com> (raw)
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
iqapi/run-state.json: introduce memory failure event
target-i386: post memory failure event to uplayer
qapi/run-state.json | 46 ++++++++++++++++++++++++++++++++++++++++++++++
target/i386/helper.c | 30 +++++++++++++++++++++++-------
target/i386/kvm.c | 5 ++++-
3 files changed, 73 insertions(+), 8 deletions(-)
--
2.11.0
next reply other threads:[~2020-09-14 13:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 13:43 zhenwei pi [this message]
2020-09-14 13:43 ` [PATCH 1/3] target-i386: seperate MCIP & MCE_MASK error reason zhenwei pi
2020-09-14 13:43 ` [PATCH 2/3] iqapi/run-state.json: introduce memory failure event zhenwei pi
2020-09-21 12:48 ` Peter Maydell
2020-09-21 13:10 ` [External] " zhenwei pi
2020-09-22 7:11 ` Paolo Bonzini
2020-09-14 13:43 ` [PATCH 3/3] target-i386: post memory failure event to uplayer zhenwei pi
2020-09-21 2:22 ` ping: [PATCH 0/3] add MEMORY_FAILURE event zhenwei pi
2020-09-21 12:09 ` Paolo Bonzini
2020-09-21 13:26 ` [External] " zhenwei pi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200914134321.958079-1-pizhenwei@bytedance.com \
--to=pizhenwei@bytedance.com \
--cc=armbru@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.