From: Atsushi Tsuji <a-tsuji@bk.jp.nec.com>
To: linux-kernel@vger.kernel.org, rostedt@goodmis.org,
Ingo Molnar <mingo@elte.hu>,
fweisbec@gmail.com, "Frank Ch. Eigler" <fche@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
paulus@samba.org, systemtap@sources.redhat.com
Subject: [PATCH 2/2] tracing: Export ftrace API for kernel modules
Date: Tue, 15 Sep 2009 19:06:32 +0900 [thread overview]
Message-ID: <4AAF6728.6010807@bk.jp.nec.com> (raw)
Export register_ and unresgister_ftrace_function_probe to modules. This can
be used by SystemTap.
Signed-off-by: Atsushi Tsuji <a-tsuji@bk.jp.nec.com>
---
kernel/trace/ftrace.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
index 5ef8f59..9c32291 100644
--- a/kernel/trace/ftrace.c
+++ b/kernel/trace/ftrace.c
@@ -2042,6 +2042,7 @@ register_ftrace_function_probe(char *glob, struct ftrace_probe_ops *ops,
return count;
}
+EXPORT_SYMBOL_GPL(register_ftrace_function_probe);
enum {
PROBE_TEST_FUNC = 1,
@@ -2108,6 +2109,7 @@ unregister_ftrace_function_probe(char *glob, struct ftrace_probe_ops *ops,
__unregister_ftrace_function_probe(glob, ops, data,
PROBE_TEST_FUNC | PROBE_TEST_DATA);
}
+EXPORT_SYMBOL_GPL(unregister_ftrace_function_probe);
void
unregister_ftrace_function_probe_func(char *glob, struct ftrace_probe_ops *ops)
--
1.5.5.1
next reply other threads:[~2009-09-15 10:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 10:06 Atsushi Tsuji [this message]
2009-09-15 10:11 ` [PATCH 2/2] tracing: Export ftrace API for kernel modules Peter Zijlstra
2009-09-15 13:43 ` Steven Rostedt
2009-09-15 14:01 ` Masami Hiramatsu
2009-09-15 14:29 ` Steven Rostedt
2009-09-16 6:09 ` Atsushi Tsuji
2009-09-16 13:04 ` Steven Rostedt
2009-09-17 0:42 ` Atsushi Tsuji
2009-09-15 23:17 ` Christoph Hellwig
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=4AAF6728.6010807@bk.jp.nec.com \
--to=a-tsuji@bk.jp.nec.com \
--cc=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=systemtap@sources.redhat.com \
/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