From: tip-bot for Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
fweisbec@gmail.com, yuanhan.liu@linux.intel.com,
rostedt@goodmis.org, tglx@linutronix.de
Subject: [tip:perf/core] tracing: Export trace_set_clr_event()
Date: Fri, 11 Mar 2011 09:52:07 GMT [thread overview]
Message-ID: <tip-56355b83e2a24ce7e1870c8479205e2cdd332225@git.kernel.org> (raw)
In-Reply-To: <1289196312-25323-1-git-send-email-yuanhan.liu@linux.intel.com>
Commit-ID: 56355b83e2a24ce7e1870c8479205e2cdd332225
Gitweb: http://git.kernel.org/tip/56355b83e2a24ce7e1870c8479205e2cdd332225
Author: Yuanhan Liu <yuanhan.liu@linux.intel.com>
AuthorDate: Mon, 8 Nov 2010 14:05:12 +0800
Committer: Steven Rostedt <rostedt@goodmis.org>
CommitDate: Thu, 10 Mar 2011 10:34:51 -0500
tracing: Export trace_set_clr_event()
Trace events belonging to a module only exists when the module is
loaded. Well, we can use trace_set_clr_event funtion to enable some
trace event at the module init routine, so that we will not miss
something while loading then module.
So, Export the trace_set_clr_event function so that module can use it.
Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
LKML-Reference: <1289196312-25323-1-git-send-email-yuanhan.liu@linux.intel.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
kernel/trace/trace_events.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
index e1d579b..e88f74f 100644
--- a/kernel/trace/trace_events.c
+++ b/kernel/trace/trace_events.c
@@ -325,6 +325,7 @@ int trace_set_clr_event(const char *system, const char *event, int set)
{
return __ftrace_set_clr_event(NULL, system, event, set);
}
+EXPORT_SYMBOL_GPL(trace_set_clr_event);
/* 128 should be much more than enough */
#define EVENT_BUF_SIZE 127
prev parent reply other threads:[~2011-03-11 9:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 6:05 [PATCH] Tracing: do export trace_set_clr_event Yuanhan Liu
2010-11-08 9:56 ` Christoph Hellwig
2010-11-08 10:14 ` Chris Wilson
2010-11-08 14:02 ` Steven Rostedt
2010-11-08 14:14 ` Christoph Hellwig
2010-11-08 14:23 ` Steven Rostedt
2010-11-09 1:44 ` Yuanhan Liu
2011-03-11 9:52 ` tip-bot for Yuanhan Liu [this message]
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=tip-56355b83e2a24ce7e1870c8479205e2cdd332225@git.kernel.org \
--to=yuanhan.liu@linux.intel.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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