From: Lin Ming <ming.m.lin@intel.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Stephane Eranian <eranian@google.com>,
Andi Kleen <andi@firstfloor.org>, Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
Arjan van de Ven <arjan@infradead.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 2/3 v3] perf: Implement Nehalem uncore pmu
Date: Fri, 10 Dec 2010 16:28:28 +0800 [thread overview]
Message-ID: <1291969708.10384.52.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <1291922670.6803.47.camel@twins>
On Fri, 2010-12-10 at 03:24 +0800, Peter Zijlstra wrote:
> On Thu, 2010-12-02 at 13:20 +0800, Lin Ming wrote:
> > +++ b/arch/x86/kernel/cpu/perf_event.c
>
> > @@ -1362,6 +1357,7 @@ int __init init_hw_perf_events(void)
> >
> > switch (boot_cpu_data.x86_vendor) {
> > case X86_VENDOR_INTEL:
> > + init_uncore_pmu();
> > err = intel_pmu_init();
> > break;
> > case X86_VENDOR_AMD:
>
> Since you're otherwise fully separated from the regular cpu driver,
> could you also grow your own early_initcall() ?
OK, will use early_initcall().
next prev parent reply other threads:[~2010-12-10 8:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 5:20 [RFC PATCH 2/3 v3] perf: Implement Nehalem uncore pmu Lin Ming
2010-12-02 5:57 ` Lin Ming
2010-12-07 6:15 ` Lin Ming
2010-12-09 19:17 ` Peter Zijlstra
2010-12-09 19:21 ` Peter Zijlstra
2010-12-09 20:15 ` Stephane Eranian
2010-12-09 20:19 ` Peter Zijlstra
2010-12-09 20:27 ` Stephane Eranian
2010-12-09 23:46 ` Stephane Eranian
2010-12-10 8:31 ` Lin Ming
2010-12-10 10:47 ` Peter Zijlstra
2010-12-10 10:52 ` Peter Zijlstra
2010-12-10 15:11 ` Cyrill Gorcunov
2010-12-11 5:49 ` Stephane Eranian
2010-12-13 8:27 ` Lin Ming
2010-12-13 16:42 ` Stephane Eranian
2010-12-13 16:51 ` Andi Kleen
2010-12-13 19:04 ` Stephane Eranian
2010-12-10 8:28 ` Lin Ming
2010-12-09 19:24 ` Peter Zijlstra
2010-12-10 8:28 ` Lin Ming [this message]
2011-01-13 17:14 ` Stephane Eranian
2011-01-17 1:29 ` Lin Ming
2011-01-17 8:44 ` Stephane Eranian
2011-01-17 10:51 ` Lin Ming
2011-01-17 10:56 ` 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=1291969708.10384.52.camel@minggr.sh.intel.com \
--to=ming.m.lin@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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