linux-kernel - Re: [PATCH 10/12] add perf counter support

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]

Message-ID: <20090811122507.GG4938@nowhere>
Date:	Tue, 11 Aug 2009 14:25:09 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Jason Baron <jbaron@...hat.com>, linux-kernel@...r.kernel.org,
	laijs@...fujitsu.com, rostedt@...dmis.org, peterz@...radead.org,
	mathieu.desnoyers@...ymtl.ca, jiayingz@...gle.com,
	mbligh@...gle.com, lizf@...fujitsu.com
Subject: Re: [PATCH 10/12] add perf counter support

On Tue, Aug 11, 2009 at 02:17:11PM +0200, Ingo Molnar wrote:
> 
> * Frederic Weisbecker <fweisbec@...il.com> wrote:
> 
> > On Mon, Aug 10, 2009 at 04:53:02PM -0400, Jason Baron wrote:
> > > Make 'perf stat -e syscalls:sys_enter_blah' work with syscall style tracepoints.
> > 
> > 
> > It would be nice to also be able to type:
> > 
> > perf stat -e syscalls:blah
> > 
> > and then having both enter/exit counters.
> 
> Plus wildcard/regex support would be nice as well in the listing of 
> events. That way one could do a shortcut of:
> 
>  perf stat -e syscalls:*
> 
> to trace all syscalls. Or:
> 
>  perf stat -e syscalls:*read*
> 
> to see all the read variants - etc.
> 
> 	Ingo


Plus filters in syscalls field. Because arguments are wrapped and post-processed,
they are not treated as usual fields.
I must confess this part is not trivial though.

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