public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, rkrcmar@redhat.com, ashok.raj@intel.com,
	haozhong.zhang@intel.com, ying.huang@intel.com
Subject: Re: [PATCH] KVM: Documentation: document MCE ioctls
Date: Thu, 9 Mar 2017 14:03:22 -0500	[thread overview]
Message-ID: <20170309140322.09464caa@redhat.com> (raw)
In-Reply-To: <42796742-3992-ed4b-7678-ec6aea1b13a8@redhat.com>

On Thu, 9 Mar 2017 13:49:06 +0100
Paolo Bonzini <pbonzini@redhat.com> wrote:

> > +struct kvm_x86_mce {
> > +	__u64 status;
> > +	__u64 addr;
> > +	__u64 misc;
> > +	__u64 mcg_status;
> > +	__u8 bank;
> > +	__u8 pad1[7];
> > +	__u64 pad2[3];
> > +};
> > +
> > +If the MCE being reported is an uncorrected error, KVM will
> > +inject it as a MCE exception into the guest (if an MCE
> > +is still in progress, a triple fault is be injected).  
> 
> If the guest MCG_STATUS register reports that an MCE is in progress, KVM
> causes an KVM_EXIT_SHUTDOWN vmexit.

Oh, that's correct. But it only happens for uncorrected errors.
So, My new paragraph would be:

If the MCE being reported is an uncorrected error, KVM will
inject it as an MCE exception into the guest. If the guest MCG_STATUS
register reports taht an MCE is in progress, KVM causes an
KVM_EXIT_SHUTDOWN vmexit.

Otherwise, if the MCE is an corrected error, KVM will just
store it in the corresponding bank (provided this bank is
not holding a previously reported uncorrected error).

  reply	other threads:[~2017-03-09 19:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 22:08 [PATCH] KVM: Documentation: document MCE ioctls Luiz Capitulino
2017-03-09 12:49 ` Paolo Bonzini
2017-03-09 19:03   ` Luiz Capitulino [this message]
2017-03-10  8:46     ` 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=20170309140322.09464caa@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=ashok.raj@intel.com \
    --cc=haozhong.zhang@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --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