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 10:27:07 -0400
From:	Masami Hiramatsu <>
To:	Ingo Molnar <>
CC:	Frederic Weisbecker <>,
	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

Ingo Molnar wrote:
> * Masami Hiramatsu <> wrote:
>> How about the following syntax?
>> <adding>
>> perf probe schedule
>> perf probe --add schedule
>> <deleting>
>> perf probe --del schedule
>> perf probe --del all	/* delete all probepoints */
>> So, this doesn't symmetric, but provides simple way to add a probe.
> agreed. For deletion, eventually this:
>   perf probe --del "*"
> should also work - as should other regexp (or glob) matches on a range 
> of existing probes.

Ah, that's a nice idea :-), it allows user to delete a group of
probes, like --del "schedule*".

> plus there should be a perf probe call to output all current probes as 
> perf probe commands - so that it can be saved (and restored).

Sure. 'perf probe --save file' & 'perf probe --restore file' will be
fine for me.

Thank you,
Masami Hiramatsu

Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division


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