From: Stephane Eranian <eranian@hpl.hp.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: B.Steinbrink@gmx.de, ak@suse.de, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: nmi_watchdog=2 regression in 2.6.21
Date: Thu, 30 Aug 2007 14:05:55 -0700 [thread overview]
Message-ID: <20070830210555.GA6635@frankl.hpl.hp.com> (raw)
In-Reply-To: <1188436919.26038.27.camel@dhcp193.mvista.com>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
Daniel,
On Wed, Aug 29, 2007 at 06:21:59PM -0700, Daniel Walker wrote:
> On Wed, 2007-08-29 at 14:24 -0700, Stephane Eranian wrote:
>
>
> > Now on Core Duo, there is no PEBS anyway, so it is okay to use counter 0
> > for NMI. The problem is that the detection code in perfctr-watchdog.c
> > treats a Core Duo and a Core 2 Duo the same way as they both have the
> > X86_FEATURE_ARCH_PERFMON bit set.
> >
> > I have attached a patch with handle the case of the Core Duo. Unfortunately,
> > I do not own one so I cannot test it. I would appreciate if you could
> > try re-applying my counter 0 -> 1 patch + this new one to see if you
> > have the problem with the NMI getting stuck.
>
> I tested your patch .. The system doesn't hang, but the NMI seems to
> disappear .. The check_nmi_watchdog() is not called, and the NMI never
> actually starts firing .. Is that what you had intended?
>
Yes, I realized I missed a small detail in the switch statement.
Could you try the new version?
Thanks.
--
-Stephane
[-- Attachment #2: coreduo.diff --]
[-- Type: text/plain, Size: 1246 bytes --]
diff --git a/arch/i386/kernel/cpu/perfctr-watchdog.c b/arch/i386/kernel/cpu/perfctr-watchdog.c
index 9b5d6af..3a945f0 100644
--- a/arch/i386/kernel/cpu/perfctr-watchdog.c
+++ b/arch/i386/kernel/cpu/perfctr-watchdog.c
@@ -613,6 +613,17 @@ static struct wd_ops intel_arch_wd_ops = {
.evntsel = MSR_ARCH_PERFMON_EVENTSEL1,
};
+/*
+ * Check for Intel Core Duo because it has a bug with PERFEVTSEL1
+ * (see Spefication Update bug AE49) and must use PERFEVTSEL0. We cannot
+ * use this counter on other processors supporting X86_FEATURE_ARCH_PERFMON
+ * because PEBS requires it.
+ */
+static inline int is_coreduo(void)
+{
+ return boot_cpu_data.x86 == 6 && boot_cpu_data.x86_model == 14;
+}
+
static void probe_nmi_watchdog(void)
{
switch (boot_cpu_data.x86_vendor) {
@@ -623,13 +634,14 @@ static void probe_nmi_watchdog(void)
wd_ops = &k7_wd_ops;
break;
case X86_VENDOR_INTEL:
- if (cpu_has(&boot_cpu_data, X86_FEATURE_ARCH_PERFMON)) {
+ if (cpu_has(&boot_cpu_data, X86_FEATURE_ARCH_PERFMON)
+ && !is_coreduo()) {
wd_ops = &intel_arch_wd_ops;
break;
}
switch (boot_cpu_data.x86) {
case 6:
- if (boot_cpu_data.x86_model > 0xd)
+ if (boot_cpu_data.x86_model > 0xe)
return;
wd_ops = &p6_wd_ops;
next prev parent reply other threads:[~2007-08-30 21:06 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 0:06 Daniel Walker
2007-08-08 14:20 ` Björn Steinbrink
2007-08-08 15:20 ` Daniel Walker
2007-08-20 16:44 ` Daniel Walker
2007-08-23 20:08 ` Michal Piotrowski
2007-08-23 21:22 ` Daniel Walker
2007-08-27 0:45 ` Who wants to maintain KR list for stable releases? (was Re: nmi_watchdog=2 regression in 2.6.21) Michal Piotrowski
2007-08-27 7:51 ` Andrew Morton
2007-08-27 9:41 ` Jeff Garzik
2007-08-27 11:35 ` Michal Piotrowski
2007-08-27 16:09 ` Adrian Bunk
2007-08-27 16:05 ` Daniel Walker
2007-08-27 11:38 ` Michal Piotrowski
2007-08-27 12:35 ` Rafael J. Wysocki
2007-08-27 15:02 ` Michal Piotrowski
2007-08-27 15:13 ` Daniel Walker
2007-08-27 15:26 ` Michal Piotrowski
2007-08-27 15:39 ` Daniel Walker
2007-08-27 17:02 ` Michal Piotrowski
2007-08-27 17:17 ` Daniel Walker
2007-08-27 19:12 ` David Rees
2007-08-29 7:42 ` Natalie Protasevich
2007-08-29 22:23 ` Adrian Bunk
2007-08-29 23:59 ` Natalie Protasevich
2007-08-30 8:51 ` Adrian Bunk
2007-08-30 15:24 ` Who wants to maintain KR list for stable releases? Stefan Richter
[not found] ` <32209efe0708300950r5787402l4d02cedd862314fd@mail.gmail.com>
2007-08-30 22:11 ` Al Boldi
2007-09-03 12:29 ` Adrian Bunk
2007-09-03 13:20 ` Stefan Richter
2007-08-30 15:54 ` Who wants to maintain KR list for stable releases? (was Re: nmi_watchdog=2 regression in 2.6.21) Bill Davidsen
2007-09-03 12:43 ` Adrian Bunk
2007-08-27 16:26 ` Daniel Walker
2007-08-27 16:44 ` Andrew Morton
2007-08-27 16:52 ` Adrian Bunk
2007-08-27 17:08 ` Daniel Walker
2007-08-27 18:26 ` Andrew Morton
2007-08-27 8:11 ` David Rees
2007-08-27 11:42 ` Michal Piotrowski
2007-08-27 14:39 ` Daniel Walker
2007-08-27 15:11 ` Michal Piotrowski
2007-08-27 17:54 ` nmi_watchdog=2 regression in 2.6.21 Stephane Eranian
2007-08-27 17:55 ` Daniel Walker
2007-08-27 22:55 ` Stephane Eranian
2007-08-27 23:07 ` Daniel Walker
2007-08-28 9:12 ` Stephane Eranian
2007-08-28 14:34 ` Daniel Walker
2007-08-28 17:05 ` Stephane Eranian
2007-08-28 18:30 ` Daniel Walker
2007-08-28 19:46 ` Stephane Eranian
2007-08-28 20:13 ` Daniel Walker
2007-08-29 21:24 ` Stephane Eranian
2007-08-30 1:21 ` Daniel Walker
2007-08-30 21:05 ` Stephane Eranian [this message]
2007-08-31 14:43 ` Daniel Walker
2007-08-31 16:21 ` Stephane Eranian
2007-08-31 16:35 ` Daniel Walker
2007-08-31 18:06 ` Björn Steinbrink
2007-09-01 0:24 ` Daniel Walker
2007-09-01 1:00 ` Björn Steinbrink
2007-09-01 1:36 ` Daniel Walker
2007-09-01 10:19 ` Andi Kleen
2007-09-01 19:51 ` Stephane Eranian
2007-09-01 20:32 ` Andi Kleen
2007-09-01 20:46 ` Daniel Walker
2007-09-01 9:12 ` Andi Kleen
2007-08-28 20:26 ` Daniel Walker
2007-08-28 20:21 ` Stephane Eranian
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=20070830210555.GA6635@frankl.hpl.hp.com \
--to=eranian@hpl.hp.com \
--cc=B.Steinbrink@gmx.de \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome