kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Huang Ying <ying.huang@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	Anthony Liguori <aliguori@us.ibm.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH -v2] QEMU-KVM: MCE: Relay UCR MCE to guest
Date: Wed, 09 Sep 2009 15:16:07 +0300	[thread overview]
Message-ID: <4AA79C87.4040003@redhat.com> (raw)
In-Reply-To: <4AA79A31.9070600@redhat.com>

On 09/09/2009 03:06 PM, Avi Kivity wrote:
> On 09/09/2009 05:28 AM, 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.
>>
>> v2:
>>
>> - Use qemu_ram_addr_from_host instead of self made one to covert from
>>    host address to guest RAM address. Thanks Anthony Liguori.
>>
>
> Patch looks good, but can you clarify the following:

Oh and I forgot - please make MCE injection optional.  Some 
installations may prefer to kill the guest and have the virtualization 
management system restart it rather than trust the guest to handle the 
MCE properly.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-09-09 12:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09  2:28 [PATCH -v2] QEMU-KVM: MCE: Relay UCR MCE to guest Huang Ying
2009-09-09 12:06 ` Avi Kivity
2009-09-09 12:16   ` Avi Kivity [this message]
2009-09-09 12:18     ` Avi Kivity
2009-09-10  2:40   ` Huang Ying
2009-09-10  9:35     ` Andi Kleen
2009-09-14  2:55       ` Huang Ying
2009-09-14  5:10         ` Avi Kivity
2009-09-16  1:09           ` Huang Ying
2009-09-16  8:10             ` Avi Kivity
2009-09-14  5:10       ` Avi Kivity
2009-09-16 17:59 ` Marcelo Tosatti
2009-09-17  1:13   ` Huang Ying
2009-09-17 21:36     ` Marcelo Tosatti
2009-09-18  3:01       ` Huang Ying

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=4AA79C87.4040003@redhat.com \
    --to=avi@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=andi@firstfloor.org \
    --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;
as well as URLs for NNTP newsgroup(s).