Messages in this thread | | | Date | Mon, 23 Apr 2012 12:57:26 +0200 | From | Jiri Olsa <> | Subject | Re: [BUG] perf stat: useless output for raw events with new event parser |
| |
On Mon, Apr 23, 2012 at 12:45:34PM +0200, Stephane Eranian wrote: > Hi, > > With the new event parser, one can express raw events field by field: > > $ perf stat -e cpu/event=0x3c,umask=0x0/,cpu/event=0xc5,umask=0x0/ noploop 1 > > The problem with this is that the output of perf stat becomes useless: > > $ perf stat -e cpu/event=0x3c,umask=0x0/,cpu/event=0xc5,umask=0x0/ noploop 1 > noploop for 1 seconds > > Performance counter stats for 'noploop 1': > > 2395038678 pmu > 10787 pmu > ^^^^^^ > 1.000802603 seconds time elapsed > > We lose the event names or encoding completely. Now for all events > expressed via this > new syntax , all we see is 'pmu'. That is pretty useless. It is hard > to decrypt the results > without some serious scripting. > > Not sure how to solve this given how the parser works. This looks like > a regression to me.
I dont think thats regression, since you use new way to express an event. Please check my answer in the other reply to Peter.
thanks, jirka
| |