From: Ingo Molnar <mingo@elte.hu>
To: Yong Wang <yong.y.wang@linux.intel.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -tip] perf_counter/x86: Fix incorrect default branch
Date: Wed, 10 Jun 2009 12:44:09 +0200 [thread overview]
Message-ID: <20090610104409.GC27724@elte.hu> (raw)
In-Reply-To: <20090610051521.GB30923@ywang-moblin2.bj.intel.com>
* Yong Wang <yong.y.wang@linux.intel.com> wrote:
> On Tue, Jun 09, 2009 at 04:25:06PM +0200, Ingo Molnar wrote:
> >
> > They dont have X86_FEATURE_ARCH_PERFMON set, right?
> >
> > I made the switch statement under the assumption that it covers all
> > existing arch-perfmon CPU models. If not, the 'default:' placement
> > would indeed be buggy.
> >
>
> OK, you are right. X86_FEATURE_ARCH_PERFMON eliminates all the old CPUs.
> However, the logic still seems not correct. Both the Core2 CPUs I'm
> using are recognized as Nehalem/Corei7. /proc/cpuinfo and cpuid outputs
> are given below.
>
> The first one:
> vendor_id : GenuineIntel
> cpu family : 6
> model : 23
> model name : Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz
> stepping : 6
>
> CPUID.0x00000001: eax=0x00010676
>
> The second one:
> vendor_id : GenuineIntel
> cpu family : 6
> model : 15
> model name : Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
> stepping : 6
>
> CPUID.0x00000001: eax=0x000006f6
>
> Looks like it's not enough to just look at boot_cpu_data.x86_model.
Yeah - i've applied the patch you sent, thanks. I'm mostly working
on NHM so i didnt notice.
Ingo
prev parent reply other threads:[~2009-06-10 10:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 7:46 [PATCH -tip] perf_counter/x86: Fix incorrect default branch Yong Wang
2009-06-09 13:23 ` Ingo Molnar
2009-06-09 13:32 ` Yong Wang
2009-06-09 14:25 ` Ingo Molnar
2009-06-10 5:15 ` Yong Wang
2009-06-10 10:44 ` Ingo Molnar [this message]
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=20090610104409.GC27724@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yong.y.wang@linux.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.