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  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:	Tue, 20 Oct 2009 19:51:19 +0200
From:	Frederic Weisbecker <>
To:	Ingo Molnar <>
Cc:	Masami Hiramatsu <>,
	Steven Rostedt <>,
	lkml <>,
	Thomas Gleixner <>,
	Arnaldo Carvalho de Melo <>,
	Mike Galbraith <>,
	Paul Mackerras <>,
	Peter Zijlstra <>,
	Christoph Hellwig <>,
	Ananth N Mavinakayanahalli <>,
	Jim Keniston <>,
	"Frank Ch. Eigler" <>,
	"H. Peter Anvin" <>,
	systemtap <>,
	DLE <>
Subject: Re: [PATCH -tip tracing/kprobes 0/9] tracing/kprobes, perf: perf
	probe and kprobe-tracer bugfixes

On Tue, Oct 20, 2009 at 08:43:34AM +0200, Ingo Molnar wrote:
> also useful for command line workflows: 'perf probe --list' output - i 
> think we users to generate func_symbol+rel_position kind of probes.
> Plus a relative position is more intuitive as well. If you see 
> 'schedule+10' versus 'schedule+102', you'll know it immediate that the 
> first one is early in the function while the second one is near the end.
> If you see 'schedule@...5' versus 'schedule@...5' that kind of 'where in 
> the function is the probe, roughly' subjective impression is lost.
> 	Ingo

Yeah, from a probe id reading POV, that's much better.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists