Re: User defined metrics for perf stat?

[Andreas Hollmann <hollmann@in.tum.de>]

Jiri, this method does not work when you pipe data to perf script.

Works with perf.data file:

./perf stat -a -I 1000 -e cycles,"cpu/config=0x6530160,name=krava/" record

/perf script -s test.py
event krava cpu -1, thread -1, time 1029898211, val 10959, ena
81192094638, run 81192094638
event krava cpu -1, thread -1, time 2043671594, val 10753, ena
81094362809, run 81094362809

does not work when using pipe

./perf stat -a -I 1000 -e cycles,"cpu/config=0x6530160,name=krava/"
record | ./perf script -s test.py

--- no output

Here the test.py

cat test.py
#!/usr/bin/env python

def stat__krava(cpu, thread, time, val, ena, run):
    print "event %s cpu %d, thread %d, time %d, val %d, ena %d, run %d" % \
          ("krava", cpu, thread, time, val, ena, run)


2016-02-03 8:48 GMT+01:00 Jiri Olsa <jolsa@redhat.com>:
> On Tue, Feb 02, 2016 at 05:24:16PM +0100, Andreas Hollmann wrote:
>> Jiri, how do you handle raw counters with this python stat__*
>> callback? What is the name of the callback?
>
> you can use 'name' term like:
>   perf stat -e cycles,"cpu/config=0x6530160,name=krava/"
>
> and use following callback in your script:
>   def stat__krava(cpu, thread, time, val, ena, run):
>
>>
>> Is there any documentation on that? Thanks!
>
> no.. ;-)
>
> I'll try to come up with something.. meanwhile please just ask,
> I'd be happy to help you
>
> thanks,
> jirka