[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4BF5D203.7000007@linux.vnet.ibm.com>
Date: Thu, 20 May 2010 17:21:23 -0700
From: Corey Ashford <cjashfor@...ux.vnet.ibm.com>
To: Peter Zijlstra <peterz@...radead.org>
CC: Lin Ming <ming.m.lin@...el.com>, Ingo Molnar <mingo@...e.hu>,
Frederic Weisbecker <fweisbec@...il.com>,
Paul Mundt <lethal@...ux-sh.org>,
"eranian@...il.com" <eranian@...il.com>,
"Gary.Mohr@...l.com" <Gary.Mohr@...l.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>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Will Deacon <will.deacon@....com>,
Maynard Johnson <mpjohn@...ibm.com>,
Carl Love <carll@...ibm.com>,
"greg@...ah.com" <greg@...ah.com>,
Kay Sievers <kay.sievers@...y.org>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [RFC][PATCH v2 11/11] perf top: demo of how to use the sysfs
interface
On 5/20/2010 1:08 PM, Peter Zijlstra wrote:
> On Wed, 2010-05-19 at 18:33 -0700, Corey Ashford wrote:
>>
>> We also need to take into account event "attributes" - other data that
>> is needed to configure a specific event. For example, think about a
>> memory controller which has a PMU can count events in a particular
>> memory range; we need to be able to supply the memory range somehow,
>
> That's that perf_event_attr is for.
>
I think the issue is that what is stuffed into perf_event_attr's fields should be done in a way that userspace tools can figure out via attribute info which is in exported by the kernel via sysfs (or eventfs, etc.)
- Corey
--
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