From: Marcelo Tosatti <mtosatti@redhat.com>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: Jin Dongming <jin.dongming@np.css.fujitsu.com>,
KVM list <kvm@vger.kernel.org>, Dean Nelson <dnelson@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Avi Kivity <avi@redhat.com>, Huang Ying <ying.huang@intel.com>
Subject: Re: [Qemu-devel] Re: [PATCH 11/11] kvm, x86: broadcast mce depending on the cpu version
Date: Fri, 15 Oct 2010 10:30:12 -0300 [thread overview]
Message-ID: <20101015133012.GA16246@amt.cnet> (raw)
In-Reply-To: <4CB7B3C5.7070102@jp.fujitsu.com>
On Fri, Oct 15, 2010 at 10:52:05AM +0900, Hidetoshi Seto wrote:
> (2010/10/15 10:06), Marcelo Tosatti wrote:
> > On Thu, Oct 14, 2010 at 05:55:28PM +0900, Jin Dongming wrote:
> >> There is no reason why SRAO event received by the main thread
> >> is the only one that being broadcasted.
> >>
> >> According to the x86 ASDM vol.3A 15.10.4.1,
> >> MCE signal is broadcast on processor version 06H_EH or later.
> >>
> >> This change is required to handle SRAR in the guest.
> >>
> >> Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
> >> Tested-by: Jin Dongming <jin.dongming@np.css.fujitsu.com>
> >> ---
> >> qemu-kvm.c | 63 +++++++++++++++++++++++++++++------------------------------
> >> 1 files changed, 31 insertions(+), 32 deletions(-)
> >
> > Why is this necessary? _AO SIGBUS should be sent to all vcpu threads and
> > main thread.
>
> Humm? If you are right, vcpu threads will receive same SRAO event twice,
> one is that received by itself and another is that received by main thread
> and forwarded by the broadcast.
>
> My understanding is (Jin, please correct me if something wrong):
> - _AO SIGBUS is sent to main thread only, and then SRAO event is
> broadcasted to all vcpu threads.
> - _AR SIGBUS is sent to a vcpu thread that tried to touch the
> unmapped poisoned page, and SRAR event is posted to the vcpu.
>
> One problem here is that SRAR is not broadcasted.
> The guest might observe the event differently, like "some cpus
> don't enter machine check."
Right.
> > Please separate bug fixes from cleanups. Very nice, thanks.
>
> Maybe this set is considered as 10 cleanups + 1 fix.
> I think this fix will be complicated one without preceding cleanups.
Why? All you need is to broadcast from vcpu context.
Please do a minimal fix separately so it can be backported, and the
cleanups can be done later once its merged upstream.
Thanks.
next prev parent reply other threads:[~2010-10-15 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 8:55 [PATCH 11/11] kvm, x86: broadcast mce depending on the cpu version Jin Dongming
2010-10-15 1:06 ` Marcelo Tosatti
2010-10-15 1:52 ` [Qemu-devel] " Hidetoshi Seto
2010-10-15 4:56 ` Huang Ying
2010-10-15 13:30 ` Marcelo Tosatti [this message]
2010-10-19 1:59 ` Hidetoshi Seto
2010-10-19 2:04 ` [PATCH uq/master 1/2] kvm, x86: ignore SRAO only when MCG_SER_P is available Hidetoshi Seto
2010-10-19 2:04 ` [PATCH uq/master 2/2] kvm, x86: broadcast mce depending on the cpu version Hidetoshi Seto
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=20101015133012.GA16246@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=dnelson@redhat.com \
--cc=jin.dongming@np.css.fujitsu.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=seto.hidetoshi@jp.fujitsu.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