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: Mon, 14 Sep 2009 08:10:56 +0300 [thread overview]
Message-ID: <4AADD060.8060100@redhat.com> (raw)
In-Reply-To: <1252896913.15717.137.camel@yhuang-dev.sh.intel.com>
On 09/14/2009 05:55 AM, Huang Ying wrote:
> Hi, Avi,
>
> On Thu, 2009-09-10 at 17:35 +0800, Andi Kleen wrote:
>
>>>> (also, I if we can't handle guest-mode SIGBUS I think it would be nice
>>>> to raise it again so the process terminates due to the SIGBUS).
>>>>
>>> For SIGBUS we can not relay to guest as MCE, we can either abort or
>>> reset SIGBUS to SIGDFL and re-raise it. Both are OK for me. You prefer
>>> the latter one?
>>>
>> I think a suitable error message and exit would be better than a plain
>> signal kill. It shouldn't look like qemu crashed due to a software
>> bug. Ideally a error message in a way that it can be parsed by libvirt etc.
>> and reported in a suitable way.
>>
> Do you agree with us about SIGBUS processing?
>
Yes.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-09-14 5:11 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
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 [this message]
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=4AADD060.8060100@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 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.