From 6bc34a93f11ca510704852d956cc195ae662adb3 Mon Sep 17 00:00:00 2001 From: Liu Bo Date: Thu, 27 Sep 2012 11:50:41 +0800 Subject: [PATCH] --- yaml --- r: 323409 b: refs/heads/master c: 9c33c512b2d3167a3580659942ee78437b1b1bc6 h: refs/heads/master i: 323407: 4fcf249e3f2a838749015924a1e40201c2d47aca v: v3 --- [refs] | 2 +- trunk/Documentation/trace/kprobetrace.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index d159cdd609d4..83e1ce5efe7e 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 7dfd8cc536dc4984ee92d9a8863ea705b955bc37 +refs/heads/master: 9c33c512b2d3167a3580659942ee78437b1b1bc6 diff --git a/trunk/Documentation/trace/kprobetrace.txt b/trunk/Documentation/trace/kprobetrace.txt index d0d0bb9e3e25..d68ea5fc812b 100644 --- a/trunk/Documentation/trace/kprobetrace.txt +++ b/trunk/Documentation/trace/kprobetrace.txt @@ -12,7 +12,7 @@ kprobes can probe (this means, all functions body except for __kprobes functions). Unlike the Tracepoint based event, this can be added and removed dynamically, on the fly. -To enable this feature, build your kernel with CONFIG_KPROBE_TRACING=y. +To enable this feature, build your kernel with CONFIG_KPROBE_EVENT=y. Similar to the events tracer, this doesn't need to be activated via current_tracer. Instead of that, add probe points via