On Fri, Apr 17, 2015 at 01:09:54PM -0700, Andi Kleen wrote:
> On Fri, Apr 17, 2015 at 05:31:26PM +0200, Jiri Olsa wrote:
> > On Wed, Apr 15, 2015 at 01:50:42PM -0700, Sukadev Bhattiprolu wrote:
> > 
> > SNIP
> > 
> > > | 
> > > |  - to blindly follow some poorly constructed vendor format with no 
> > > |    high level structure, that IMHO didn't work very well when OProfile 
> > > |    was written, and misrepresenting it as 'symbolic event names'.
> > > | 
> > > |    Take a look at:
> > > | 
> > > |      https://download.01.org/perfmon/HSW/Haswell_core_V17.json
> > > | 
> > > |    and weep.
> > > 
> > > Evil vendor formats, but to be fair, here is what _we_ have today:
> > > 
> > >   perf stat -e r10068,r20036,r40060,r40ac sleep 1
> > 
> > hum, you could also use the 'cpu/event=.../' syntax right?
> 
> That's even worse -- same hex numbers, just more redundancy.

no, it's far more readable then the rXXXX format,
you can just put in whatevent is in the spec..
event,umask,any etc and dont bother with making
rXXXX value

but I mentioned it just to give the whole picture,
I agree that we need the symbolic names support

jirka
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Reply via email to