From: "Yan, Zheng" <zheng.z.yan@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH v2 4/4] perf/x86/uncore: modularize Intel uncore driver
Date: Fri, 25 Apr 2014 22:44:43 +0800 [thread overview]
Message-ID: <535A74DB.2070709@intel.com> (raw)
In-Reply-To: <20140425143501.GH11096@twins.programming.kicks-ass.net>
On 04/25/2014 10:35 PM, Peter Zijlstra wrote:
> On Fri, Apr 25, 2014 at 10:06:15PM +0800, Yan, Zheng wrote:
>> the uncore driver does not support NHM/WSM-EP (I don't know the module numbers for NHM/WSM-EP, maybe I'm wrong)
>
> My wsm-ep has /sys/bus/event_source/devices/uncore so I suppose the
> driver loaded. Its model 44 fwiw.
>
> Also, from the uncore driver:
>
> switch (boot_cpu_data.x86_model) {
> case 26: /* Nehalem */
> case 30:
> case 37: /* Westmere */
> case 44:
> msr_uncores = nhm_msr_uncores;
> break;
>
looks like the uncore in NHM/WSM-EP is the same as uncore in desktop version NHM/WSM.
Regards
Yan, Zheng
prev parent reply other threads:[~2014-04-25 14:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 6:03 [PATCH v2 4/4] perf/x86/uncore: modularize Intel uncore driver Yan, Zheng
2014-03-20 8:27 ` Peter Zijlstra
2014-04-18 10:53 ` Ingo Molnar
2014-04-18 16:49 ` Andi Kleen
2014-04-21 2:18 ` Yan, Zheng
2014-04-22 11:35 ` Ingo Molnar
2014-04-23 14:55 ` Stephane Eranian
2014-04-24 8:14 ` Ingo Molnar
2014-04-24 10:25 ` Yan, Zheng
2014-04-24 10:36 ` Stephane Eranian
2014-04-24 10:37 ` Yan, Zheng
2014-04-24 11:27 ` Peter Zijlstra
2014-04-25 13:17 ` Yan, Zheng
2014-04-25 13:55 ` Peter Zijlstra
2014-04-25 14:06 ` Yan, Zheng
2014-04-25 14:35 ` Peter Zijlstra
2014-04-25 14:44 ` Yan, Zheng [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=535A74DB.2070709@intel.com \
--to=zheng.z.yan@intel.com \
--cc=acme@infradead.org \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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 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.