Em Fri, Feb 11, 2011 at 12:31:11PM -0800, Arun Sharma escreveu: > On Fri, Feb 11, 2011 at 12:21 PM, Can Hankendi <hankendi@xxxxxxxxx> wrote: > > Thanks for the reply. I've tried perf record -C 0 -e cycles sleep 1 but i > > received an error: Couldn't record kernel reference relocation symbol. Is it > > possible to create per core report by using perf stat -C 0,1 so that I can > > have individual stats for each core? > > # ./perf stat -e cycles -A -a -- sleep 1 > > Performance counter stats for 'sleep 1': > > CPU0 2,145,862,116 cycles > CPU1 2,146,131,064 cycles > CPU2 2,146,021,047 cycles > [...] > > and you can grep out only the CPUs you're looking for. > > If you're looking to do something more complicated that really > requires hacking up a script, I wrapped the perf_event_open syscall in > python via swig. > > sys.py --cpulist > > may be interesting. > > http://perfmon2.git.sourceforge.net/git/gitweb.cgi?p=perfmon2/libpfm4;a=blob;f=python/sys.py;h=e3a44f24174b979694e2588592f759010b77621e;hb=f70e032b5b69cf5aa6f7e0da746b1817c64341e9 Interesting, have you seen the python binding in tip/perf/core? - Arnaldo -- To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html