From: Huang Ying <ying.huang@intel.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, Andi Kleen <andi@firstfloor.org>,
Anthony Liguori <aliguori@us.ibm.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH -v3] QEMU-KVM: MCE: Relay UCR MCE to guest
Date: Mon, 21 Sep 2009 10:23:47 +0800 [thread overview]
Message-ID: <1253499827.15717.530.camel@yhuang-dev.sh.intel.com> (raw)
In-Reply-To: <20090918170535.GA9100@amt.cnet>
On Sat, 2009-09-19 at 01:05 +0800, Marcelo Tosatti wrote:
> On Fri, Sep 18, 2009 at 03:58:59PM +0800, Huang Ying wrote:
> > UCR (uncorrected recovery) MCE is supported in recent Intel CPUs,
> > where some hardware error such as some memory error can be reported
> > without PCC (processor context corrupted). To recover from such MCE,
> > the corresponding memory will be unmapped, and all processes accessing
> > the memory will be killed via SIGBUS.
> >
> > For KVM, if QEMU/KVM is killed, all guest processes will be killed
> > too. So we relay SIGBUS from host OS to guest system via a UCR MCE
> > injection. Then guest OS can isolate corresponding memory and kill
> > necessary guest processes only. SIGBUS sent to main thread (not VCPU
> > threads) will be broadcast to all VCPU threads as UCR MCE.
> >
> > v3:
> >
> > - Re-raise SIGBUS for SIGBUS not from MCE
> > - Kill itself for error in kvm_inject_x86_mce
>
> This is broken, non-MCE SIGBUS causes qemu-kvm to call the sigbus
> handler in a loop.
Sorry. I tested the wrong branch in previous development. I will fix
this.
> BTW, how are you testing this and what guests have been tested?
I use a self-made kernel module to simulate SIGBUS from MCE handler to
qemu. Until now, only Linux guest has been tested.
Best Regards,
Huang Ying
prev parent reply other threads:[~2009-09-21 2:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 7:58 [PATCH -v3] QEMU-KVM: MCE: Relay UCR MCE to guest Huang Ying
2009-09-18 17:05 ` Marcelo Tosatti
2009-09-21 2:23 ` Huang Ying [this message]
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=1253499827.15717.530.camel@yhuang-dev.sh.intel.com \
--to=ying.huang@intel.com \
--cc=aliguori@us.ibm.com \
--cc=andi@firstfloor.org \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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