linux-kernel - Re: [RFD] Kprobes/Kretprobes perf 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]

Date:	Thu, 13 Aug 2009 10:02:45 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Masami Hiramatsu <mhiramat@...hat.com>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Lai Jiangshan <laijs@...fujitsu.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	Jiaying Zhang <jiayingz@...gle.com>,
	Martin Bligh <mbligh@...gle.com>,
	Li Zefan <lizf@...fujitsu.com>, Jason Baron <jbaron@...hat.com>
Subject: Re: [RFD] Kprobes/Kretprobes perf support


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

>> Speaking about your patches. You told recently you would be 
>> willing to implement a perf support for kprobes, right? :-)
>
> Hmm, perhaps, I meant a profiling 
> interface(http://lkml.org/lkml/2009/7/24/240). However, that is 
> interesting idea too.

Note that profiling via perf and perfcounters is a very young 
project, but already far more capable:

 - It is a generic framework. If you provide an event source, the 
   full framework will understand and support your events and will 
   expose it to users: 'perf stat' works, 'perf record',
   'perf report', 'perf top' all works the upcoming 'perf trace'
   and the upcoming 'perf view' GUI will all understand it. These 
   are all different modes of analysis, from the high-level 
   statistics bits, through profiling, down to lowlevel tracing - 
   based on the same stream of data.

 - It's very flexible: there's per cpu, per task or per workload 
   hierarchy stats/profiling/tracing.

 - It can do call-chain graph recording/reporting
   (try "perf record -g -f -a sleep 1" + "perf report")

 - There's a standard syscall interface to all this, making it 
   readily accessible and pushing it into apps and tools.

 - Your events can and will mix with all the other events. So there 
   can be hardware PMU events, software counters, tracepoints, etc. 
   - all in the same data file.

So while there's still a lot of work to do all across the 
perfcounters spectrum, it generally would be nice to expose kprobes 
events via perfcounters.

	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/