linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@elte.hu>,
	Masami Hiramatsu <mhiramat@redhat.com>,
	Mel Gorman <mel@csn.ul.ie>, Steven Rostedt <rostedt@goodmis.org>,
	Randy Dunlap <rdunlap@xenotime.net>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Roland McGrath <roland@redhat.com>,
	Christoph Hellwig <hch@infradead.org>,
	Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
	Oleg Nesterov <oleg@redhat.com>, Mark Wielaard <mjw@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Jim Keniston <jkenisto@linux.vnet.ibm.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	"Frank Ch. Eigler" <fche@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH v4 0/13] Uprobes v4
Date: Tue, 18 May 2010 16:49:44 -0400	[thread overview]
Message-ID: <20100518204944.GA6959@Krystal> (raw)
In-Reply-To: <20100518165826.20070.11594.sendpatchset@localhost6.localdomain6>

* Srikar Dronamraju (srikar@linux.vnet.ibm.com) wrote:
> Uprobes Patches
> 
> Changelog from v3:
>   - Reverted to background page replacement as suggested by Peter Zijlstra.

Why ?

I'm not sure we reached any concensus about the need for a background page
replacement.

Thanks,

Mathieu

>   - Dso in 'perf probe' can be either be a short name or a absolute path.
>   - Addressed comments from Masami, Frederic, Steven on traceevents and perf
> 
> Changelog from v2:
>   - Addressed comments from Oleg, including removal of interrupt context
>     handlers, reverting background page replacement in favour of
>     access_process_vm().
> 
>   - Provides perf interface for uprobes.
> 
> Changelog from v1:
>  - Added trace_event interface for uprobes.
>  - Addressed comments from Andrew Morton and Randy Dunlap.
> 
> For previous postings: please refer: http://lkml.org/lkml/2010/5/6/273
> and http://lkml.org/lkml/2010/3/20/107
> 
> 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 is a rework based on suggestions from discussions on lkml
> in January and March this year (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.
> 
> 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-process "execution out of line (XOL) area". Currently XOL area is
> allocated as one page vma.
> 
> 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.
> 
> - Rebase to -tip tree. (targeted for v5)
> - Allowing probes across fork.
> - Allowing probes per-executable/per dso.
> - Allow multiple probes to share a probepoint.
> - Return probes.
> - Support for other architectures.
> - Uprobes booster.
> - Merge uprobes and kprobes trace_event.
> - replace macro with bits in inat table.
> 
> The current patchset is based on 2.6.34.
> 
> Please do provide your valuable comments.
> 
> Thanks in advance.
> Srikar
> 
> Srikar Dronamraju (10):
>  1.  X86 instruction analysis: Move Macro W to insn.h
>  2.  mm: Move replace_page() to mm/memory.c
>  3.  user_bkpt: User Space Breakpoint Assistance Layer
>  4.  user_bkpt: X86 details for User space breakpoint assistance
>  5.  user_bkpt: Slot allocation for Execution out of line
>  6.  uprobes: Uprobes Implementation
>  7.  uprobes: X86 details for Uprobes
>  8.  samples: Uprobes samples
>  9.  uprobes: Uprobes Documentation patch
>  10. trace: Share common code for uprobes/kprobes traceevents
>  11. trace: uprobes trace_event interface
>  12. perf: Dont adjust symbols if lookup is by name.
>  13. perf: perf interface for uprobes.
> 
>  Documentation/uprobes.txt          |  236 ++++++++++
>  arch/Kconfig                       |   31 ++
>  arch/x86/Kconfig                   |    2 +
>  arch/x86/include/asm/insn.h        |    7 +
>  arch/x86/include/asm/thread_info.h |    2 +
>  arch/x86/include/asm/user_bkpt.h   |   43 ++
>  arch/x86/kernel/Makefile           |    3 +
>  arch/x86/kernel/kprobes.c          |    7 -
>  arch/x86/kernel/signal.c           |   17 +
>  arch/x86/kernel/uprobes.c          |   77 ++++
>  arch/x86/kernel/user_bkpt.c        |  572 ++++++++++++++++++++++++
>  fs/exec.c                          |    4 +
>  include/linux/mm.h                 |    4 +
>  include/linux/mm_types.h           |    4 +
>  include/linux/sched.h              |    4 +
>  include/linux/uprobes.h            |  169 ++++++++
>  include/linux/user_bkpt.h          |  305 +++++++++++++
>  include/linux/user_bkpt_xol.h      |   40 ++
>  kernel/Makefile                    |    3 +
>  kernel/fork.c                      |   20 +
>  kernel/trace/Kconfig               |   13 +
>  kernel/trace/Makefile              |    1 +
>  kernel/trace/trace.h               |   11 +
>  kernel/trace/trace_kprobe.c        |   76 +----
>  kernel/trace/trace_probe.h         |  111 +++++
>  kernel/trace/trace_uprobe.c        |  839 ++++++++++++++++++++++++++++++++++++
>  kernel/uprobes.c                   |  681 +++++++++++++++++++++++++++++
>  kernel/user_bkpt.c                 |  589 +++++++++++++++++++++++++
>  kernel/user_bkpt_xol.c             |  302 +++++++++++++
>  mm/ksm.c                           |  112 -----
>  mm/memory.c                        |  120 +++++
>  samples/Kconfig                    |    7 +
>  samples/Makefile                   |    2 +-
>  samples/uprobes/Makefile           |   17 +
>  samples/uprobes/uprobe_example.c   |   83 ++++
>  tools/perf/builtin-probe.c         |   38 ++-
>  tools/perf/builtin-top.c           |   20 -
>  tools/perf/util/event.c            |   20 +
>  tools/perf/util/event.h            |    1 +
>  tools/perf/util/probe-event.c      |  237 +++++++++--
>  tools/perf/util/probe-event.h      |    9 +-
>  tools/perf/util/probe-finder.h     |    1 +
>  tools/perf/util/symbol.c           |    6 +-
>  43 files changed, 4576 insertions(+), 270 deletions(-)

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com

  parent reply	other threads:[~2010-05-18 20:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18 16:58 [PATCH v4 0/13] Uprobes v4 Srikar Dronamraju
2010-05-18 16:58 ` [PATCH v4 1/13] X86 instruction analysis: Move Macro W to insn.h Srikar Dronamraju
2010-05-18 16:58 ` [PATCH v4 2/13] mm: Move replace_page to mm/memory.c Srikar Dronamraju
2010-05-18 16:58 ` [PATCH v4 3/13] User Space Breakpoint Assistance Layer Srikar Dronamraju
2010-05-18 16:59 ` [PATCH v4 4/13] x86 support for User space breakpoint assistance Srikar Dronamraju
2010-05-18 16:59 ` [PATCH v4 5/13] Slot allocation for execution out of line (XOL) Srikar Dronamraju
2010-05-18 16:59 ` [PATCH v4 6/13] Uprobes Implementation Srikar Dronamraju
2010-05-18 16:59 ` [PATCH v4 7/13] x86 support for Uprobes Srikar Dronamraju
2010-05-18 16:59 ` [PATCH v4 8/13] samples: Uprobes samples Srikar Dronamraju
2010-05-18 17:00 ` [PATCH v4 9/13] Uprobes documentation Srikar Dronamraju
2010-05-18 17:00 ` [PATCH v4 10/13] trace: Common code for kprobes/uprobes traceevents Srikar Dronamraju
2010-05-18 17:23   ` Masami Hiramatsu
2010-05-19  6:21     ` Srikar Dronamraju
2010-05-19 14:44       ` Masami Hiramatsu
2010-05-18 17:00 ` [PATCH v4 11/13] trace: uprobes trace_event interface Srikar Dronamraju
2010-05-25  2:22   ` Steven Rostedt
2010-05-25 12:23     ` Srikar Dronamraju
2010-05-18 17:00 ` [PATCH v4 12/13] perf: Dont adjust symbols on name lookup Srikar Dronamraju
2010-05-18 17:00 ` [PATCH v4 13/13] perf: perf interface for uprobes Srikar Dronamraju
2010-05-18 20:49 ` Mathieu Desnoyers [this message]
2010-05-19  6:08   ` [PATCH v4 0/13] Uprobes v4 Srikar Dronamraju
2010-05-19 14:15     ` Mathieu Desnoyers
2010-05-19 14:17     ` Peter Zijlstra
2010-05-19 17:38       ` Srikar Dronamraju
2010-05-19 17:45         ` Frank Ch. Eigler
2010-05-19 17:54         ` Peter Zijlstra
2010-05-20  2:26           ` Srikar Dronamraju

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=20100518204944.GA6959@Krystal \
    --to=mathieu.desnoyers@efficios.com \
    --cc=akpm@linux-foundation.org \
    --cc=ananth@in.ibm.com \
    --cc=fche@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=hch@infradead.org \
    --cc=hpa@zytor.com \
    --cc=jkenisto@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mel@csn.ul.ie \
    --cc=mhiramat@redhat.com \
    --cc=mingo@elte.hu \
    --cc=mjw@redhat.com \
    --cc=oleg@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rdunlap@xenotime.net \
    --cc=rjw@sisk.pl \
    --cc=roland@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=srikar@linux.vnet.ibm.com \
    --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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).