linux-kernel - Re: [PATCH -tip] perf_counter tools: shorten names for events

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:	Sun, 5 Jul 2009 02:32:39 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Anton Blanchard <anton@...ba.org>
Cc:	Roland Dreier <rdreier@...co.com>,
	Jaswinder Singh Rajput <jaswinder@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -tip] perf_counter tools: shorten names for events


* Anton Blanchard <anton@...ba.org> wrote:

> 
> Hi,
> 
> > IMHO "L1d" is too abbreviated for it to be obvious that it means L1 data
> > cache.  If you want something really short maybe "L1-d$" might be a
> > little clearer, but I stil like "L1-dcache" best.
> 
> There's one problem with L1-d$-* for event names. It took me a few goes
> before I realised I was being hit by bash variable expansion:
> 
> 
> #  perf stat -e L1-d$-loads ls
> 
>  usage: perf stat [<options>] <command>
> 
> ...
> 
> 
> # perf stat -e 'L1-d$-loads' ls
> 
>  Performance counter stats for 'ls':
> 
>         1273291  L1-d$-loads             
> 
>     0.004434037  seconds time elapsed
> 
> 
> I also prefer the more verbose L1-dcache-* names, and since we 
> support aliases its mostly a matter of screen real estate when 
> printing out the statistics.

ok - mind sending a patch for this?

	Ingo
--
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/