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
| ||
|
Message-ID: <ad7a95ae0910191859l6e0246b8u8634fac5b8ec0770@mail.gmail.com> Date: Mon, 19 Oct 2009 21:59:42 -0400 From: Ashwin Chaugule <ashbertslists@...il.com> To: Masami Hiramatsu <mhiramat@...hat.com> Cc: Frederic Weisbecker <fweisbec@...il.com>, Steven Rostedt <rostedt@...dmis.org>, Ingo Molnar <mingo@...e.hu>, lkml <linux-kernel@...r.kernel.org>, Thomas Gleixner <tglx@...utronix.de>, Paul Mackerras <paulus@...ba.org>, a.p.zijlstra@...llo.nl Subject: Re: [PATCH -tip tracing/kprobes 0/9] tracing/kprobes, perf: perf probe and kprobe-tracer bugfixes On Mon, Oct 19, 2009 at 8:30 PM, Masami Hiramatsu <mhiramat@...hat.com> wrote: > > Actually, perf-probe can add tracepoint-like events. It will allow you > to probe function inside by both C-source-line level and address level. > perf-probe already supports inline function too. > > Currently, even its syntax is unstable, but you can add an event inside > some function which is at cfile.c line 100, as below; > > perf probe -P 'p:probe1 cfile.c:100' > > and you can trace it by using perf record as same as other tracepoints > > perf record -f -e kprobes:myprobe:record -F 1 -a ls > > >> Alternately, I think even dynamic trace could provide similar insight >> with perfevents ? If none of this is already done, I plan to work on >> this in my spare time and would like to team up with anyone else >> interested. > > Yes, it's done as I said above. > But it still has long TODO list, including support type of arguments, > arrays, fields of structures and so on (of course, defining useful > syntax too). So any comments and contributes are welcome :-) > Excellent ! Time to give it a spin :) Cheers, Ashwin -- 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/
Powered by blists - more mailing lists