From: Marcelo Tosatti <mtosatti@redhat.com>
To: Huang Ying <ying.huang@intel.com>
Cc: Avi Kivity <avi@redhat.com>, Andi Kleen <andi@firstfloor.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] Ignore SRAO MCE if another MCE is being processed
Date: Tue, 27 Apr 2010 13:12:15 -0300 [thread overview]
Message-ID: <20100427161215.GE23249@amt.cnet> (raw)
In-Reply-To: <1272352249.24125.19.camel@yhuang-dev.sh.intel.com>
On Tue, Apr 27, 2010 at 03:10:49PM +0800, Huang Ying wrote:
> In common cases, guest SRAO MCE will cause corresponding poisoned page
> be un-mapped in host and SIGBUS be sent to QEMU-KVM, then QEMU-KVM
> will relay the MCE to guest OS.
>
> But it is possible that the poisoned page is accessed in guest after
> un-mapped in host and before MCE is relayed to guest OS. So that, the
> SRAR SIGBUS is sent to QEMU-KVM before the SRAO SIGBUS, and if
> QEMU-KVM relays them to guest OS one by one, guest system may reset,
> because the SRAO MCE may be triggered while the SRAR MCE is being
> processed. In fact, the SRAO MCE can be ignored in this situation, so
> that the guest system is given opportunity to survive.
>
> Signed-off-by: Huang Ying <ying.huang@intel.com>
> ---
> qemu-kvm.c | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> --- a/qemu-kvm.c
> +++ b/qemu-kvm.c
> @@ -1610,6 +1610,19 @@ static void flush_queued_work(CPUState *
> pthread_cond_broadcast(&qemu_work_cond);
> }
>
> +static int kvm_mce_in_exception(CPUState *env)
> +{
> + struct kvm_msr_entry msr_mcg_status = {
> + .index = MSR_MCG_STATUS,
> + };
> + int r;
> +
> + r = kvm_get_msrs(env, &msr_mcg_status, 1);
> + if (r == -1 || r == 0)
> + return -1;
> + return !!(msr_mcg_status.data & MCG_STATUS_MCIP);
> +}
> +
> static void kvm_on_sigbus(CPUState *env, siginfo_t *siginfo)
> {
> #if defined(KVM_CAP_MCE) && defined(TARGET_I386)
> @@ -1630,6 +1643,15 @@ static void kvm_on_sigbus(CPUState *env,
> mce.misc = (MCM_ADDR_PHYS << 6) | 0xc;
> mce.mcg_status = MCG_STATUS_MCIP | MCG_STATUS_EIPV;
> } else {
> + /*
> + * If there is an MCE excpetion being processed, ignore
> + * this SRAO MCE
> + */
> + r = kvm_mce_in_exception(env);
> + if (r == -1)
> + fprintf(stderr, "Failed to get MCE status\n");
> + else if (r)
> + return;
> /* Fake an Intel architectural Memory scrubbing UCR */
> mce.status = MCI_STATUS_VAL | MCI_STATUS_UC | MCI_STATUS_EN
> | MCI_STATUS_MISCV | MCI_STATUS_ADDRV | MCI_STATUS_S
> @@ -2475,6 +2497,12 @@ static void kvm_do_inject_x86_mce(void *
> struct kvm_x86_mce_data *data = _data;
> int r;
>
> + /* If there is an MCE excpetion being processed, ignore this SRAO MCE */
> + r = kvm_mce_in_exception(data->env);
> + if (r == -1)
> + fprintf(stderr, "Failed to get MCE status\n");
> + else if (r && !(data->mce->status & MCI_STATUS_AR))
> + return;
Don't you need to set the OVER bit in the MCI_STATUS register when
this happens?
Unrelated to this patch, it would be nice if you can share the testing
code.
next prev parent reply other threads:[~2010-04-27 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 7:10 [PATCH] Ignore SRAO MCE if another MCE is being processed Huang Ying
2010-04-27 16:12 ` Marcelo Tosatti [this message]
2010-04-28 6:08 ` Huang Ying
2010-04-28 16:33 ` Avi Kivity
2010-04-29 1:03 ` Huang Ying
2010-04-28 16:28 ` Marcelo Tosatti
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=20100427161215.GE23249@amt.cnet \
--to=mtosatti@redhat.com \
--cc=andi@firstfloor.org \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=ying.huang@intel.com \
/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