From: Srikar Dronamraju <srikar@linux.vnet.ibm.com> To: Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@elte.hu> Cc: Steven Rostedt <rostedt@goodmis.org>, Srikar Dronamraju <srikar@linux.vnet.ibm.com>, Linux-mm <linux-mm@kvack.org>, Arnaldo Carvalho de Melo <acme@infradead.org>, Linus Torvalds <torvalds@linux-foundation.org>, Jonathan Corbet <corbet@lwn.net>, Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>, Christoph Hellwig <hch@infradead.org>, Ananth N Mavinakayanahalli <ananth@in.ibm.com>, Thomas Gleixner <tglx@linutronix.de>, Andi Kleen <andi@firstfloor.org>, Oleg Nesterov <oleg@redhat.com>, Andrew Morton <akpm@linux-foundation.org>, Jim Keniston <jkenisto@linux.vnet.ibm.com>, Roland McGrath <roland@hack.frob.com>, SystemTap <systemtap@sources.redhat.com>, LKML <linux-kernel@vger.kernel.org> Subject: [PATCH v3 2.6.39-rc1-tip 0/26] 0: Uprobes patchset with perf probe support Date: Fri, 01 Apr 2011 20:02:23 +0530 [thread overview] Message-ID: <20110401143223.15455.19844.sendpatchset@localhost6.localdomain6> (raw) This patchset implements Uprobes which enables you to dynamically break into any routine in a user space application and collect information non-disruptively. This patchset resolves most of the comments on the previous posting http://lkml.org/lkml/2011/3/14/171/. It also adds perf probe support for user space tracing. This patchset applies on top of tip commit acf359c95697. Uprobes Patches This patchset implements inode based uprobes which are specified as <file>:<offset> where offset is the offset from start of the map. The probehit overhead is around 3X times the overhead from pid based patchset. When a uprobe is registered, Uprobes makes a copy of the probed instruction, replaces the first byte(s) of the probed instruction with a breakpoint instruction. (Uprobes uses background page replacement mechanism and ensures that the breakpoint affects only that process.) When a CPU hits the breakpoint instruction, Uprobes gets notified of trap and finds the associated uprobe. It then executes the associated handler. Uprobes single-steps its copy of the probed instruction and resumes execution of the probed process at the instruction following the probepoint. Instruction copies to be single-stepped are stored in a per-mm "execution out of line (XOL) area". Currently XOL area is allocated as one page vma. For previous postings: please refer: http://lkml.org/lkml/2010/12/16/65 http://lkml.org/lkml/2010/8/25/165 http://lkml.org/lkml/2010/7/27/121 http://lkml.org/lkml/2010/7/12/67 http://lkml.org/lkml/2010/7/8/239 http://lkml.org/lkml/2010/6/29/299 http://lkml.org/lkml/2010/6/14/41 http://lkml.org/lkml/2010/3/20/107 and http://lkml.org/lkml/2010/5/18/307 This patchset is a rework based on suggestions from discussions on lkml in September, March and January 2010 (http://lkml.org/lkml/2010/1/11/92, http://lkml.org/lkml/2010/1/27/19, http://lkml.org/lkml/2010/3/20/107 and http://lkml.org/lkml/2010/3/31/199 ). This implementation of uprobes doesnt depend on utrace. Advantages of uprobes over conventional debugging include: 1. Non-disruptive. Unlike current ptrace based mechanisms, uprobes tracing wouldnt involve signals, stopping threads and context switching between the tracer and tracee. 2. Much better handling of multithreaded programs because of XOL. Current ptrace based mechanisms use single stepping inline, i.e they copy back the original instruction on hitting a breakpoint. In such mechanisms tracers have to stop all the threads on a breakpoint hit or tracers will not be able to handle all hits to the location of interest. Uprobes uses execution out of line, where the instruction to be traced is analysed at the time of breakpoint insertion and a copy of instruction is stored at a different location. On breakpoint hit, uprobes jumps to that copied location and singlesteps the same instruction and does the necessary fixups post singlestepping. 3. Multiple tracers for an application. Multiple uprobes based tracer could work in unison to trace an application. There could one tracer that could be interested in generic events for a particular set of process. While there could be another tracer that is just interested in one specific event of a particular process thats part of the previous set of process. 4. Corelating events from kernels and userspace. Uprobes could be used with other tools like kprobes, tracepoints or as part of higher level tools like perf to give a consolidated set of events from kernel and userspace. In future we could look at a single backtrace showing application, library and kernel calls. Here is the list of TODO Items. - Breakpoint handling should co-exist with singlestep/blockstep from another tracer/debugger. - Queue and dequeue signals delivered from the singlestep till completion of postprocessing. - Prefiltering (i.e filtering at the time of probe insertion) - Return probes. - Support for other architectures. - Uprobes booster. - replace macro W with bits in inat table. To try please fetch using git fetch \ git://git.kernel.org/pub/scm/linux/kernel/git/srikar/linux-uprobes.git \ tip_inode_uprobes_010411:tip_inode_uprobes Please refer "[RFC] [PATCH 2.6.37-rc5-tip 20/20] 20: tracing: uprobes trace_event infrastructure" on how to use uprobe_tracer. Please do provide your valuable comments. Thanks in advance. Srikar Srikar Dronamraju(26) 0: Uprobes patchset with perf probe support 1: mm: replace_page() loses static attribute 2: mm: Move replace_page() to mm/memory.c 3: X86 specific breakpoint definitions. 4: uprobes: Breakground page replacement. 5: uprobes: Adding and remove a uprobe in a rb tree. 6: Uprobes: register/unregister probes. 7: x86: analyze instruction and determine fixups. 8: uprobes: store/restore original instruction. 9: uprobes: mmap and fork hooks. 10: x86: architecture specific task information. 11: uprobes: task specific information. 12: uprobes: slot allocation for uprobes 13: uprobes: get the breakpoint address. 14: x86: x86 specific probe handling 15: uprobes: Handing int3 and singlestep exception. 16: x86: uprobes exception notifier for x86. 17: uprobes: register a notifier for uprobes. 18: uprobes: commonly used filters. 19: tracing: Extract out common code for kprobes/uprobes traceevents. 20: tracing: uprobes trace_event interface 21: Signed-off-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com> 22: perf: rename target_module to target 23: perf: show possible probes in a given executable file or library. 24: perf: perf interface for uprobes 25: perf: Documentation for perf uprobes 26: uprobes: filter chain Documentation/trace/uprobetrace.txt | 94 ++ arch/Kconfig | 4 + arch/x86/Kconfig | 3 + arch/x86/include/asm/thread_info.h | 2 + arch/x86/include/asm/uprobes.h | 55 ++ arch/x86/kernel/Makefile | 1 + arch/x86/kernel/signal.c | 14 + arch/x86/kernel/uprobes.c | 614 +++++++++++++ include/linux/mm.h | 2 + include/linux/mm_types.h | 9 + include/linux/sched.h | 3 + include/linux/uprobes.h | 197 ++++ kernel/Makefile | 1 + kernel/fork.c | 10 + kernel/trace/Kconfig | 20 + kernel/trace/Makefile | 2 + kernel/trace/trace.h | 5 + kernel/trace/trace_kprobe.c | 861 +------------------ kernel/trace/trace_probe.c | 753 ++++++++++++++++ kernel/trace/trace_probe.h | 160 ++++ kernel/trace/trace_uprobe.c | 803 +++++++++++++++++ kernel/uprobes.c | 1474 +++++++++++++++++++++++++++++++ mm/ksm.c | 62 -- mm/memory.c | 62 ++ mm/mmap.c | 6 + tools/perf/Documentation/perf-probe.txt | 21 +- tools/perf/builtin-probe.c | 26 +- tools/perf/util/probe-event.c | 431 ++++++++-- tools/perf/util/probe-event.h | 12 +- tools/perf/util/symbol.c | 8 + tools/perf/util/symbol.h | 1 + 31 files changed, 4714 insertions(+), 1002 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Srikar Dronamraju <srikar@linux.vnet.ibm.com> To: Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@elte.hu> Cc: Steven Rostedt <rostedt@goodmis.org>, Srikar Dronamraju <srikar@linux.vnet.ibm.com>, Linux-mm <linux-mm@kvack.org>, Arnaldo Carvalho de Melo <acme@infradead.org>, Linus Torvalds <torvalds@linux-foundation.org>, Jonathan Corbet <corbet@lwn.net>, Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>, Christoph Hellwig <hch@infradead.org>, Ananth N Mavinakayanahalli <ananth@in.ibm.com>, Thomas Gleixner <tglx@linutronix.de>, Andi Kleen <andi@firstfloor.org>, Oleg Nesterov <oleg@redhat.com>, Andrew Morton <akpm@linux-foundation.org>, Jim Keniston <jkenisto@linux.vnet.ibm.com>, Roland McGrath <roland@hack.frob.com>, SystemTap <systemtap@sources.redhat.com>, LKML <linux-kernel@vger.kernel.org> Subject: [PATCH v3 2.6.39-rc1-tip 0/26] 0: Uprobes patchset with perf probe support Date: Fri, 01 Apr 2011 20:02:23 +0530 [thread overview] Message-ID: <20110401143223.15455.19844.sendpatchset@localhost6.localdomain6> (raw) This patchset implements Uprobes which enables you to dynamically break into any routine in a user space application and collect information non-disruptively. This patchset resolves most of the comments on the previous posting http://lkml.org/lkml/2011/3/14/171/. It also adds perf probe support for user space tracing. This patchset applies on top of tip commit acf359c95697. Uprobes Patches This patchset implements inode based uprobes which are specified as <file>:<offset> where offset is the offset from start of the map. The probehit overhead is around 3X times the overhead from pid based patchset. When a uprobe is registered, Uprobes makes a copy of the probed instruction, replaces the first byte(s) of the probed instruction with a breakpoint instruction. (Uprobes uses background page replacement mechanism and ensures that the breakpoint affects only that process.) When a CPU hits the breakpoint instruction, Uprobes gets notified of trap and finds the associated uprobe. It then executes the associated handler. Uprobes single-steps its copy of the probed instruction and resumes execution of the probed process at the instruction following the probepoint. Instruction copies to be single-stepped are stored in a per-mm "execution out of line (XOL) area". Currently XOL area is allocated as one page vma. For previous postings: please refer: http://lkml.org/lkml/2010/12/16/65 http://lkml.org/lkml/2010/8/25/165 http://lkml.org/lkml/2010/7/27/121 http://lkml.org/lkml/2010/7/12/67 http://lkml.org/lkml/2010/7/8/239 http://lkml.org/lkml/2010/6/29/299 http://lkml.org/lkml/2010/6/14/41 http://lkml.org/lkml/2010/3/20/107 and http://lkml.org/lkml/2010/5/18/307 This patchset is a rework based on suggestions from discussions on lkml in September, March and January 2010 (http://lkml.org/lkml/2010/1/11/92, http://lkml.org/lkml/2010/1/27/19, http://lkml.org/lkml/2010/3/20/107 and http://lkml.org/lkml/2010/3/31/199 ). This implementation of uprobes doesnt depend on utrace. Advantages of uprobes over conventional debugging include: 1. Non-disruptive. Unlike current ptrace based mechanisms, uprobes tracing wouldnt involve signals, stopping threads and context switching between the tracer and tracee. 2. Much better handling of multithreaded programs because of XOL. Current ptrace based mechanisms use single stepping inline, i.e they copy back the original instruction on hitting a breakpoint. In such mechanisms tracers have to stop all the threads on a breakpoint hit or tracers will not be able to handle all hits to the location of interest. Uprobes uses execution out of line, where the instruction to be traced is analysed at the time of breakpoint insertion and a copy of instruction is stored at a different location. On breakpoint hit, uprobes jumps to that copied location and singlesteps the same instruction and does the necessary fixups post singlestepping. 3. Multiple tracers for an application. Multiple uprobes based tracer could work in unison to trace an application. There could one tracer that could be interested in generic events for a particular set of process. While there could be another tracer that is just interested in one specific event of a particular process thats part of the previous set of process. 4. Corelating events from kernels and userspace. Uprobes could be used with other tools like kprobes, tracepoints or as part of higher level tools like perf to give a consolidated set of events from kernel and userspace. In future we could look at a single backtrace showing application, library and kernel calls. Here is the list of TODO Items. - Breakpoint handling should co-exist with singlestep/blockstep from another tracer/debugger. - Queue and dequeue signals delivered from the singlestep till completion of postprocessing. - Prefiltering (i.e filtering at the time of probe insertion) - Return probes. - Support for other architectures. - Uprobes booster. - replace macro W with bits in inat table. To try please fetch using git fetch \ git://git.kernel.org/pub/scm/linux/kernel/git/srikar/linux-uprobes.git \ tip_inode_uprobes_010411:tip_inode_uprobes Please refer "[RFC] [PATCH 2.6.37-rc5-tip 20/20] 20: tracing: uprobes trace_event infrastructure" on how to use uprobe_tracer. Please do provide your valuable comments. Thanks in advance. Srikar Srikar Dronamraju(26) 0: Uprobes patchset with perf probe support 1: mm: replace_page() loses static attribute 2: mm: Move replace_page() to mm/memory.c 3: X86 specific breakpoint definitions. 4: uprobes: Breakground page replacement. 5: uprobes: Adding and remove a uprobe in a rb tree. 6: Uprobes: register/unregister probes. 7: x86: analyze instruction and determine fixups. 8: uprobes: store/restore original instruction. 9: uprobes: mmap and fork hooks. 10: x86: architecture specific task information. 11: uprobes: task specific information. 12: uprobes: slot allocation for uprobes 13: uprobes: get the breakpoint address. 14: x86: x86 specific probe handling 15: uprobes: Handing int3 and singlestep exception. 16: x86: uprobes exception notifier for x86. 17: uprobes: register a notifier for uprobes. 18: uprobes: commonly used filters. 19: tracing: Extract out common code for kprobes/uprobes traceevents. 20: tracing: uprobes trace_event interface 21: Signed-off-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com> 22: perf: rename target_module to target 23: perf: show possible probes in a given executable file or library. 24: perf: perf interface for uprobes 25: perf: Documentation for perf uprobes 26: uprobes: filter chain Documentation/trace/uprobetrace.txt | 94 ++ arch/Kconfig | 4 + arch/x86/Kconfig | 3 + arch/x86/include/asm/thread_info.h | 2 + arch/x86/include/asm/uprobes.h | 55 ++ arch/x86/kernel/Makefile | 1 + arch/x86/kernel/signal.c | 14 + arch/x86/kernel/uprobes.c | 614 +++++++++++++ include/linux/mm.h | 2 + include/linux/mm_types.h | 9 + include/linux/sched.h | 3 + include/linux/uprobes.h | 197 ++++ kernel/Makefile | 1 + kernel/fork.c | 10 + kernel/trace/Kconfig | 20 + kernel/trace/Makefile | 2 + kernel/trace/trace.h | 5 + kernel/trace/trace_kprobe.c | 861 +------------------ kernel/trace/trace_probe.c | 753 ++++++++++++++++ kernel/trace/trace_probe.h | 160 ++++ kernel/trace/trace_uprobe.c | 803 +++++++++++++++++ kernel/uprobes.c | 1474 +++++++++++++++++++++++++++++++ mm/ksm.c | 62 -- mm/memory.c | 62 ++ mm/mmap.c | 6 + tools/perf/Documentation/perf-probe.txt | 21 +- tools/perf/builtin-probe.c | 26 +- tools/perf/util/probe-event.c | 431 ++++++++-- tools/perf/util/probe-event.h | 12 +- tools/perf/util/symbol.c | 8 + tools/perf/util/symbol.h | 1 + 31 files changed, 4714 insertions(+), 1002 deletions(-) -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2011-04-01 14:42 UTC|newest] Thread overview: 150+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-01 14:32 Srikar Dronamraju [this message] 2011-04-01 14:32 ` [PATCH v3 2.6.39-rc1-tip 0/26] 0: Uprobes patchset with perf probe support Srikar Dronamraju 2011-04-01 14:32 ` [PATCH v3 2.6.39-rc1-tip 1/26] 1: mm: replace_page() loses static attribute Srikar Dronamraju 2011-04-01 14:32 ` Srikar Dronamraju 2011-04-01 14:32 ` [PATCH v3 2.6.39-rc1-tip 2/26] 2: mm: Move replace_page() to mm/memory.c Srikar Dronamraju 2011-04-01 14:32 ` Srikar Dronamraju 2011-04-01 14:33 ` [PATCH v3 2.6.39-rc1-tip 3/26] 3: X86 specific breakpoint definitions Srikar Dronamraju 2011-04-01 14:33 ` Srikar Dronamraju 2011-04-01 14:33 ` [PATCH v3 2.6.39-rc1-tip 4/26] 4: uprobes: Breakground page replacement Srikar Dronamraju 2011-04-01 14:33 ` Srikar Dronamraju 2011-04-18 12:20 ` Peter Zijlstra 2011-04-18 12:20 ` Peter Zijlstra 2011-04-01 14:33 ` [PATCH v3 2.6.39-rc1-tip 5/26] 5: uprobes: Adding and remove a uprobe in a rb tree Srikar Dronamraju 2011-04-01 14:33 ` Srikar Dronamraju 2011-04-18 12:20 ` Peter Zijlstra 2011-04-18 12:20 ` Peter Zijlstra 2011-04-01 14:33 ` [PATCH v3 2.6.39-rc1-tip 6/26] 6: Uprobes: register/unregister probes Srikar Dronamraju 2011-04-01 14:33 ` Srikar Dronamraju 2011-04-02 0:26 ` Stephen Wilson 2011-04-02 0:26 ` Stephen Wilson 2011-04-02 0:53 ` Srikar Dronamraju 2011-04-02 0:53 ` Srikar Dronamraju 2011-04-02 1:29 ` Stephen Wilson 2011-04-02 1:29 ` Stephen Wilson 2011-04-18 12:20 ` Peter Zijlstra 2011-04-18 12:20 ` Peter Zijlstra 2011-04-01 14:33 ` [PATCH v3 2.6.39-rc1-tip 7/26] 7: x86: analyze instruction and determine fixups Srikar Dronamraju 2011-04-01 14:33 ` Srikar Dronamraju 2011-04-19 13:29 ` Steven Rostedt 2011-04-19 13:29 ` Steven Rostedt 2011-04-21 17:31 ` Srikar Dronamraju 2011-04-21 17:31 ` Srikar Dronamraju 2011-04-21 17:52 ` Peter Zijlstra 2011-04-21 17:52 ` Peter Zijlstra 2011-04-01 14:33 ` [PATCH v3 2.6.39-rc1-tip 8/26] 8: uprobes: store/restore original instruction Srikar Dronamraju 2011-04-01 14:33 ` Srikar Dronamraju 2011-04-18 16:12 ` Peter Zijlstra 2011-04-18 16:12 ` Peter Zijlstra 2011-04-01 14:34 ` [PATCH v3 2.6.39-rc1-tip 9/26] 9: uprobes: mmap and fork hooks Srikar Dronamraju 2011-04-01 14:34 ` Srikar Dronamraju 2011-04-18 16:21 ` Peter Zijlstra 2011-04-18 16:21 ` Peter Zijlstra 2011-04-18 16:29 ` Peter Zijlstra 2011-04-18 16:29 ` Peter Zijlstra 2011-04-19 6:45 ` Srikar Dronamraju 2011-04-19 6:45 ` Srikar Dronamraju 2011-04-01 14:34 ` [PATCH v3 2.6.39-rc1-tip 10/26] 10: x86: architecture specific task information Srikar Dronamraju 2011-04-01 14:34 ` Srikar Dronamraju 2011-04-01 14:34 ` [PATCH v3 2.6.39-rc1-tip 11/26] 11: uprobes: task specific information Srikar Dronamraju 2011-04-01 14:34 ` Srikar Dronamraju 2011-04-01 14:34 ` [PATCH v3 2.6.39-rc1-tip 12/26] 12: uprobes: slot allocation for uprobes Srikar Dronamraju 2011-04-01 14:34 ` Srikar Dronamraju 2011-04-18 16:46 ` Peter Zijlstra 2011-04-18 16:46 ` Peter Zijlstra 2011-04-19 6:26 ` Srikar Dronamraju 2011-04-19 6:26 ` Srikar Dronamraju 2011-04-19 9:02 ` Peter Zijlstra 2011-04-19 9:02 ` Peter Zijlstra 2011-04-19 9:11 ` Peter Zijlstra 2011-04-19 9:11 ` Peter Zijlstra 2011-04-20 13:40 ` Eric Paris 2011-04-20 13:40 ` Eric Paris 2011-04-20 14:51 ` Frank Ch. Eigler 2011-04-20 14:51 ` Frank Ch. Eigler 2011-04-20 15:16 ` Stephen Smalley 2011-04-20 15:16 ` Stephen Smalley 2011-04-21 14:11 ` Srikar Dronamraju 2011-04-21 14:11 ` Srikar Dronamraju 2011-04-21 14:45 ` Eric Paris 2011-04-21 14:45 ` Eric Paris 2011-04-21 16:14 ` Roland McGrath 2011-04-21 16:14 ` Roland McGrath 2011-04-21 16:59 ` Srikar Dronamraju 2011-04-21 16:59 ` Srikar Dronamraju 2011-04-01 14:35 ` [PATCH v3 2.6.39-rc1-tip 13/26] 13: uprobes: get the breakpoint address Srikar Dronamraju 2011-04-01 14:35 ` Srikar Dronamraju 2011-04-18 16:47 ` Peter Zijlstra 2011-04-18 16:47 ` Peter Zijlstra 2011-04-01 14:35 ` [PATCH v3 2.6.39-rc1-tip 14/26] 14: x86: x86 specific probe handling Srikar Dronamraju 2011-04-01 14:35 ` Srikar Dronamraju 2011-04-18 16:55 ` Peter Zijlstra 2011-04-18 16:55 ` Peter Zijlstra 2011-04-19 5:43 ` Srikar Dronamraju 2011-04-19 5:43 ` Srikar Dronamraju 2011-04-18 16:57 ` Peter Zijlstra 2011-04-18 16:57 ` Peter Zijlstra 2011-04-01 14:35 ` [PATCH v3 2.6.39-rc1-tip 15/26] 15: uprobes: Handing int3 and singlestep exception Srikar Dronamraju 2011-04-01 14:35 ` Srikar Dronamraju 2011-04-19 13:03 ` Peter Zijlstra 2011-04-19 13:03 ` Peter Zijlstra 2011-04-19 13:12 ` Steven Rostedt 2011-04-19 13:12 ` Steven Rostedt 2011-04-21 17:10 ` Srikar Dronamraju 2011-04-21 17:10 ` Srikar Dronamraju 2011-04-21 17:41 ` Peter Zijlstra 2011-04-21 17:41 ` Peter Zijlstra 2011-04-19 13:39 ` Peter Zijlstra 2011-04-19 13:39 ` Peter Zijlstra 2011-04-21 17:03 ` Srikar Dronamraju 2011-04-21 17:03 ` Srikar Dronamraju 2011-04-01 14:35 ` [PATCH v3 2.6.39-rc1-tip 16/26] 16: x86: uprobes exception notifier for x86 Srikar Dronamraju 2011-04-01 14:35 ` Srikar Dronamraju 2011-04-01 14:35 ` [PATCH v3 2.6.39-rc1-tip 17/26] 17: uprobes: register a notifier for uprobes Srikar Dronamraju 2011-04-01 14:35 ` Srikar Dronamraju 2011-04-19 13:54 ` Peter Zijlstra 2011-04-19 13:54 ` Peter Zijlstra 2011-04-01 14:36 ` [PATCH v3 2.6.39-rc1-tip 18/26] 18: uprobes: commonly used filters Srikar Dronamraju 2011-04-01 14:36 ` Srikar Dronamraju 2011-04-05 1:26 ` Masami Hiramatsu 2011-04-05 1:26 ` Masami Hiramatsu 2011-04-19 13:57 ` Peter Zijlstra 2011-04-19 13:57 ` Peter Zijlstra 2011-04-21 11:09 ` Srikar Dronamraju 2011-04-21 11:09 ` Srikar Dronamraju 2011-04-21 11:37 ` Peter Zijlstra 2011-04-21 11:37 ` Peter Zijlstra 2011-04-21 11:49 ` Srikar Dronamraju 2011-04-21 11:49 ` Srikar Dronamraju 2011-04-01 14:36 ` [PATCH v3 2.6.39-rc1-tip 19/26] 19: tracing: Extract out common code for kprobes/uprobes traceevents Srikar Dronamraju 2011-04-01 14:36 ` Srikar Dronamraju 2011-04-01 14:36 ` [PATCH v3 2.6.39-rc1-tip 20/26] 20: tracing: uprobes trace_event interface Srikar Dronamraju 2011-04-01 14:36 ` Srikar Dronamraju 2011-04-01 14:36 ` [PATCH v3 2.6.39-rc1-tip 21/26] 21: Signed-off-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com> Srikar Dronamraju 2011-04-01 14:36 ` Srikar Dronamraju 2011-04-01 14:47 ` [RESEND] [PATCH v3 2.6.39-rc1-tip 21/26] 21: Uprobe tracer documentation " Srikar Dronamraju 2011-04-01 14:47 ` Srikar Dronamraju 2011-04-01 14:36 ` [PATCH v3 2.6.39-rc1-tip 22/26] 22: perf: rename target_module to target Srikar Dronamraju 2011-04-01 14:36 ` Srikar Dronamraju 2011-04-04 10:06 ` Masami Hiramatsu 2011-04-04 10:06 ` Masami Hiramatsu 2011-04-06 23:46 ` Srikar Dronamraju 2011-04-06 23:46 ` Srikar Dronamraju 2011-04-01 14:37 ` [PATCH v3 2.6.39-rc1-tip 23/26] 23: perf: show possible probes in a given executable file or library Srikar Dronamraju 2011-04-01 14:37 ` Srikar Dronamraju 2011-04-04 10:15 ` Masami Hiramatsu 2011-04-04 10:15 ` Masami Hiramatsu 2011-04-06 22:50 ` Srikar Dronamraju 2011-04-06 22:50 ` Srikar Dronamraju 2011-04-01 14:37 ` [PATCH v3 2.6.39-rc1-tip 24/26] 24: perf: perf interface for uprobes Srikar Dronamraju 2011-04-01 14:37 ` Srikar Dronamraju 2011-04-01 14:37 ` [PATCH v3 2.6.39-rc1-tip 25/26] 25: perf: Documentation for perf uprobes Srikar Dronamraju 2011-04-01 14:37 ` Srikar Dronamraju 2011-04-01 14:37 ` [PATCH v3 2.6.39-rc1-tip 26/26] 26: uprobes: filter chain Srikar Dronamraju 2011-04-01 14:37 ` Srikar Dronamraju 2011-04-05 1:27 ` Masami Hiramatsu 2011-04-05 1:27 ` Masami Hiramatsu 2011-04-06 22:41 ` Srikar Dronamraju 2011-04-06 22:41 ` Srikar Dronamraju 2011-04-07 3:19 ` Masami Hiramatsu 2011-04-07 3:19 ` Masami Hiramatsu
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20110401143223.15455.19844.sendpatchset@localhost6.localdomain6 \ --to=srikar@linux.vnet.ibm.com \ --cc=acme@infradead.org \ --cc=akpm@linux-foundation.org \ --cc=ananth@in.ibm.com \ --cc=andi@firstfloor.org \ --cc=corbet@lwn.net \ --cc=hch@infradead.org \ --cc=jkenisto@linux.vnet.ibm.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=masami.hiramatsu.pt@hitachi.com \ --cc=mingo@elte.hu \ --cc=oleg@redhat.com \ --cc=peterz@infradead.org \ --cc=roland@hack.frob.com \ --cc=rostedt@goodmis.org \ --cc=systemtap@sources.redhat.com \ --cc=tglx@linutronix.de \ --cc=torvalds@linux-foundation.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.