From: Paolo Bonzini <pbonzini@redhat.com>
To: zhenwei pi <pizhenwei@bytedance.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [External] Re: [PATCH 2/3] iqapi/run-state.json: introduce memory failure event
Date: Tue, 22 Sep 2020 09:11:38 +0200 [thread overview]
Message-ID: <08d688b5-fe64-6bb7-3fa8-9e976640041a@redhat.com> (raw)
In-Reply-To: <348159b8-0e10-ab93-42ca-5e6d586d5abc@bytedance.com>
On 21/09/20 15:10, zhenwei pi wrote:
>>
> Right, to make architecture-neutral, how about these changes:
> 'PC-RAM' -> 'guest-memory'
> 'guest-mce' -> 'guest-mce-inject'
> 'guest-triple-fault' -> 'guest-mce-fault'
Perhaps we should have three fields
1) recipient: 'hypervisor' or 'guest'
2) action: 'ignore', 'inject', 'fatal'
3) kind: 'action-optional' or 'action-required'
And possibly:
4) recursive: true or false
On x86 "recursive" would be set if MCIP=1.
Paolo
next prev parent reply other threads:[~2020-09-22 7:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 13:43 [PATCH 0/3] add MEMORY_FAILURE event zhenwei pi
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 [this message]
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=08d688b5-fe64-6bb7-3fa8-9e976640041a@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=mtosatti@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pizhenwei@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).