From: Don Zickus <dzickus@redhat.com>
To: Shaun Ruffell <sruffell@digium.com>
Cc: linux-kernel@vger.kernel.org,
Cyrill Gorcunov <gorcunov@openvz.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [regression 2.6.39-rc2][bisected] "perf, x86: P4 PMU - Read proper MSR register to catch" and NMIs
Date: Wed, 6 Apr 2011 20:16:58 -0400 [thread overview]
Message-ID: <20110407001658.GW12642@redhat.com> (raw)
In-Reply-To: <20110406223036.GA15721@digium.com>
On Wed, Apr 06, 2011 at 05:30:36PM -0500, Shaun Ruffell wrote:
> Hello Don,
>
> I was able to bisect it down to commit 242214f9c1eeaae40, but I'm not
> certain where to go from here. Is this something that is already known
> or is there more information I should try to collect?
Nope, this is an ongoing issue. What happened was the perf P4 nmi handler
was swallowing all the NMIs. My patch fixed that and exposed a double NMI
problem. We have been chasing it for a couple of months. I think Cyril
was finally able to duplicate it (as he wrote the P4 code). I have
confidence that he will find a fix for it soon. :-)
Thanks for the report though!
Cheers,
Don
next prev parent reply other threads:[~2011-04-07 0:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 22:30 [regression 2.6.39-rc2][bisected] "perf, x86: P4 PMU - Read proper MSR register to catch" and NMIs Shaun Ruffell
2011-04-07 0:16 ` Don Zickus [this message]
2011-04-07 3:18 ` Cyrill Gorcunov
2011-04-07 14:38 ` Shaun Ruffell
2011-04-07 14:43 ` Cyrill Gorcunov
2011-04-13 19:33 ` Maciej Rutecki
2011-04-13 20:01 ` Cyrill Gorcunov
2011-04-13 20:35 ` Shaun Ruffell
2011-04-13 20:43 ` Cyrill Gorcunov
2011-04-13 21:22 ` Don Zickus
2011-04-13 21:25 ` Cyrill Gorcunov
2011-04-13 21:53 ` Shaun Ruffell
2011-04-14 14:30 ` Shaun Ruffell
2011-04-14 14:33 ` Cyrill Gorcunov
2011-04-14 6:47 ` Ingo Molnar
2011-04-14 7:51 ` Cyrill Gorcunov
2011-04-14 8:05 ` Ingo Molnar
2011-04-14 9:27 ` Cyrill Gorcunov
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=20110407001658.GW12642@redhat.com \
--to=dzickus@redhat.com \
--cc=gorcunov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sruffell@digium.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