Re: User defined metrics for perf stat?

[Jiri Olsa <jolsa@redhat.com>]

On Fri, Feb 05, 2016 at 03:12:04PM +0100, Andreas Hollmann wrote:
> 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)

right, we probably don't transfer the name term through the pipe,
I'll check on that..

jirka