From: Wanpeng Li <wanpeng.li@linux.intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Ben Serebrin <serebrin@google.com>,
kvm@vger.kernel.org, stable@vger.kernel.org, luto@amacapital.net,
jankiszka@siemens.com
Subject: Re: [PATCH] KVM: VMX: Preserve host CR4.MCE value while in guest mode.
Date: Mon, 20 Apr 2015 06:59:13 +0800 [thread overview]
Message-ID: <20150419225913.GA8627@kernel> (raw)
In-Reply-To: <5530DD72.7010801@redhat.com>
On Fri, Apr 17, 2015 at 12:16:18PM +0200, Paolo Bonzini wrote:
>
>
>On 17/04/2015 07:10, Wanpeng Li wrote:
>>> >
>>> >Before the change, if guest CR4.MCE==0, then the machine check is
>>> >escalated to Catastrophic Error (CATERR) and the machine dies.
>> Could you point out which section of SDM describes that the machine check
>> is escalated to a CATERR if CR4.MCE==0?
>
>It's under the description of "Interrupt 18--Machine-Check Exception (#MC)":
>
> The machine-check mechanism is enabled by setting the MCE flag in
> control register CR4. [...] If the machine-check mechanism is not
> enabled (the MCE flag in control register CR4 is clear), a
> machine-check exception causes the processor to enter the shutdown
> state.
>
>This of course also applies whenever the non-root mode CR4 (*not* the
>shadow CR4 in the VMCS!) has the MCE flag cleared.
Got it, thanks, :)
Regards,
Wanpeng Li
>
>Paolo
next prev parent reply other threads:[~2015-04-19 22:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 18:58 [PATCH] KVM: VMX: Preserve host CR4.MCE value while in guest mode Ben Serebrin
2015-04-16 20:42 ` Venkatesh Srinivas
2015-04-17 5:10 ` Wanpeng Li
2015-04-17 10:16 ` Paolo Bonzini
2015-04-17 16:03 ` Benjamin Serebrin
2015-04-19 22:59 ` Wanpeng Li [this message]
2015-04-17 8:55 ` Greg KH
2015-04-17 10:10 ` Paolo Bonzini
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=20150419225913.GA8627@kernel \
--to=wanpeng.li@linux.intel.com \
--cc=jankiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=pbonzini@redhat.com \
--cc=serebrin@google.com \
--cc=stable@vger.kernel.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.