Re: [perf] howto switch from pfmon
From: Ingo Molnar
Date: Tue Jun 23 2009 - 09:39:10 EST
* Peter Zijlstra <a.p.zijlstra@xxxxxxxxx> wrote:
> On Tue, 2009-06-23 at 15:14 +0200, Ingo Molnar wrote:
> > * Brice Goglin <Brice.Goglin@xxxxxxxx> wrote:
> > > Hello,
> > >
> > > I am trying to play with perfcounters in current git (actually in
> > > latest mmotm). I'd like to reproduce what I previously did with
> > > pfmon, but I couldn't so far.
> > >
> > > Something like
> > > pfmon --follow-exec 'foobar' -e
> > > CPU_TO_DRAM_REQUESTS_TO_TARGET_NODE:LOCAL_TO_0,CPU_TO_DRAM_REQUESTS_TO_TARGET_NODE:LOCAL_TO_1
> > > -- <shell script>
> > > gives the number of memory accesses to dram node #0 and #1 for all
> > > processes whose name matches 'foobar'.
> > >
> > > So there are several questions here:
> > > 1) is it possible to specify counter names like the above or do we have
> > > to use raw counter numbers? I tried raw numbers from  without
> > > success. How am I supposed to find and specify these raw numbers?
> > > 2) how do we specify "subevents"?
> > > 3) is there anything similar to --follow-exec, or --follow-pthreads for
> > > getting separated outputs for each thread?
> > >
> > > I guess there are still a lot of things on the TODOlist but I'd
> > > like to understand a bit more where things are going. Sorry I
> > > didn't read all the archives about this, there are way too many of
> > > them recently :)
> > Yeah, there's indeed still a lot on the TODO list :-)
> > CPU_TO_DRAM_REQUESTS_TO_TARGET_NODE is a Barcelona hardware event,
> > so if you know that it maps to raw ID 0x100000e0 then you can always
> > extend the events that 'perf' knows about via raw events:
> > $ perf stat -e cycles -e instructions -e r1000ffe0 ./hackbench 10
> > Time: 0.186
> > Performance counter stats for './hackbench 10':
> > 4381248335 cycles
> > 1964394846 instructions # 0.448 IPC
> > 838 raw 0x1000ffe0
> > 0.215382037 seconds time elapsed.
> Just to clarify, The event code is 1E0h, and Ingo used a FFh unit mask.
> These are combined using the arch masks below:
> #define K7_EVNTSEL_EVENT_MASK 0x7000000FFULL
> #define K7_EVNTSEL_UNIT_MASK 0x00000FF00ULL
> to form the raw event code used: 0x1000ffe0
Yes. The individual node mappings are 01, 02 .. 80 - ff is 'all 8
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/