linux-kernel - Re: 'perf upgrade' (was: Re: [PATCH v9 00/11] Add support for JSON event files.)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 18 Apr 2015 15:05:36 +0200
From:	Jiri Olsa <jolsa@...hat.com>
To:	Andi Kleen <ak@...ux.intel.com>
Cc:	Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>,
	Ingo Molnar <mingo@...nel.org>,
	Michael Ellerman <mpe@...erman.id.au>, mingo@...hat.com,
	Arnaldo Carvalho de Melo <acme@...nel.org>,
	peterz@...radead.org, namhyung@...nel.org,
	linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
	Pekka Enberg <penberg@....fi>,
	Arnaldo Carvalho de Melo <acme@...radead.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Borislav Petkov <bp@...en8.de>
Subject: Re: 'perf upgrade' (was: Re: [PATCH v9 00/11] Add support for JSON
 event files.)

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/