[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1273489913.15998.103.camel@minggr.sh.intel.com>
Date: Mon, 10 May 2010 19:11:53 +0800
From: Lin Ming <ming.m.lin@...el.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Paul Mundt <lethal@...ux-sh.org>, Ingo Molnar <mingo@...e.hu>,
Frederic Weisbecker <fweisbec@...il.com>,
"eranian@...il.com" <eranian@...il.com>,
"Gary.Mohr@...l.com" <Gary.Mohr@...l.com>,
Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>,
Paul Mackerras <paulus@...ba.org>,
"David S. Miller" <davem@...emloft.net>,
Russell King <rmk+kernel@....linux.org.uk>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [RFC][PATCH 3/9] perf: export registerred pmus via sysfs
On Mon, 2010-05-10 at 19:04 +0800, Peter Zijlstra wrote:
> On Mon, 2010-05-10 at 18:58 +0800, Lin Ming wrote:
> > Take Nehalem core and uncore pmu as an example,
> >
> > core pmu sits under /sys/devices/system/cpu/cpuN/pmu_id with ID 0,
> >
> > But uncore pmu is shared by cpus within package, where should it sit
> > under?
>
> I already gave you the answer to that:
>
> /sys/devices/system/cpu/cpuN/nodeN/
>
> the uncore pmu is the memory controller (aka node) pmu.
Ah, much clear now.
perf_event_register_pmu needs another paramter, like
perf_event_register_pmu(struct pmu *pmu, int pmu_type);
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists