linux-kernel - Re: [RFC PATCH tracing/kprobes 0/5] tracing/kprobes, perf: perf kprobe 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: <20090930120418.GB7618@elte.hu>
Date:	Wed, 30 Sep 2009 14:04:18 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Masami Hiramatsu <mhiramat@...hat.com>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	lkml <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Mike Galbraith <efault@....de>,
	Paul Mackerras <paulus@...ba.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Christoph Hellwig <hch@...radead.org>,
	Ananth N Mavinakayanahalli <ananth@...ibm.com>,
	Jim Keniston <jkenisto@...ibm.com>,
	"Frank Ch. Eigler" <fche@...hat.com>,
	systemtap <systemtap@...rces.redhat.com>,
	DLE <dle-develop@...ts.sourceforge.net>
Subject: Re: [RFC PATCH tracing/kprobes 0/5] tracing/kprobes,  perf: perf
	kprobe support


* Masami Hiramatsu <mhiramat@...hat.com> wrote:

> Masami Hiramatsu wrote:
>>
>> Hi,
>>
>> These patches introduce perf kprobe command and update kprobe-tracer.
>> perf kprobe command allows you to add new probe points by C line number
>> and local variable names.
>
> Last week, Arnaldo and I talked about this command, and he suggested 
> that the command would be better 'perf probe', because it would be 
> able to cover both of kernel space (by kprobes) and user space (by 
> uprobes).

Agreed.

> Basically, I agree with his idea. But I think we may need to consider 
> more flexible syntax for that purpose before we support uprobes. In 
> this area, SystemTap has done big advance, we can see how many 
> varieties of syntax it has by 'man stapprobes'.
>
> And also, it's hard to decide it without real uprobe-tracer (and 
> uprobes too!) implementation on ftrace. So, I think it is better to 
> continue using 'perf kprobe' in this time.
>
> But it's worth to add to todo list. :)

I'd still name it 'perf probe', even if initially it supports kprobes.

	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/