From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>
Subject: [PATCH 07/13] ftrace: Add ops parameter to ftrace_startup/shutdown functions
Date: Wed, 18 May 2011 22:11:58 -0400 [thread overview]
Message-ID: <20110519021256.229981824@goodmis.org> (raw)
In-Reply-To: <20110519021151.600991800@goodmis.org>
[-- Attachment #1: 0007-ftrace-Add-ops-parameter-to-ftrace_startup-shutdown-.patch --]
[-- Type: text/plain, Size: 3602 bytes --]
From: Steven Rostedt <srostedt@redhat.com>
In order to allow different ops to enable different functions,
the ftrace_startup() and ftrace_shutdown() functions need the
ops parameter passed to them.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
kernel/trace/ftrace.c | 28 ++++++++++++++--------------
1 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
index 065f1e6..8fef1d9 100644
--- a/kernel/trace/ftrace.c
+++ b/kernel/trace/ftrace.c
@@ -1522,10 +1522,8 @@ static void ftrace_startup_enable(int command)
ftrace_run_update_code(command);
}
-static void ftrace_startup(int command)
+static void ftrace_startup(struct ftrace_ops *ops, int command)
{
- struct ftrace_ops *ops = &global_ops;
-
if (unlikely(ftrace_disabled))
return;
@@ -1539,10 +1537,8 @@ static void ftrace_startup(int command)
ftrace_startup_enable(command);
}
-static void ftrace_shutdown(int command)
+static void ftrace_shutdown(struct ftrace_ops *ops, int command)
{
- struct ftrace_ops *ops = &global_ops;
-
if (unlikely(ftrace_disabled))
return;
@@ -2362,7 +2358,7 @@ static void __enable_ftrace_function_probe(void)
return;
__register_ftrace_function(&trace_probe_ops);
- ftrace_startup(0);
+ ftrace_startup(&global_ops, 0);
ftrace_probe_registered = 1;
}
@@ -2381,7 +2377,7 @@ static void __disable_ftrace_function_probe(void)
/* no more funcs left */
__unregister_ftrace_function(&trace_probe_ops);
- ftrace_shutdown(0);
+ ftrace_shutdown(&global_ops, 0);
ftrace_probe_registered = 0;
}
@@ -3267,6 +3263,10 @@ void __init ftrace_init(void)
#else
+struct ftrace_ops global_ops = {
+ .func = ftrace_stub,
+};
+
static int __init ftrace_nodyn_init(void)
{
ftrace_enabled = 1;
@@ -3277,8 +3277,8 @@ device_initcall(ftrace_nodyn_init);
static inline int ftrace_init_dyn_debugfs(struct dentry *d_tracer) { return 0; }
static inline void ftrace_startup_enable(int command) { }
/* Keep as macros so we do not need to define the commands */
-# define ftrace_startup(command) do { } while (0)
-# define ftrace_shutdown(command) do { } while (0)
+# define ftrace_startup(ops, command) do { } while (0)
+# define ftrace_shutdown(ops, command) do { } while (0)
# define ftrace_startup_sysctl() do { } while (0)
# define ftrace_shutdown_sysctl() do { } while (0)
#endif /* CONFIG_DYNAMIC_FTRACE */
@@ -3583,7 +3583,7 @@ int register_ftrace_function(struct ftrace_ops *ops)
goto out_unlock;
ret = __register_ftrace_function(ops);
- ftrace_startup(0);
+ ftrace_startup(&global_ops, 0);
out_unlock:
mutex_unlock(&ftrace_lock);
@@ -3602,7 +3602,7 @@ int unregister_ftrace_function(struct ftrace_ops *ops)
mutex_lock(&ftrace_lock);
ret = __unregister_ftrace_function(ops);
- ftrace_shutdown(0);
+ ftrace_shutdown(&global_ops, 0);
mutex_unlock(&ftrace_lock);
return ret;
@@ -3825,7 +3825,7 @@ int register_ftrace_graph(trace_func_graph_ret_t retfunc,
ftrace_graph_return = retfunc;
ftrace_graph_entry = entryfunc;
- ftrace_startup(FTRACE_START_FUNC_RET);
+ ftrace_startup(&global_ops, FTRACE_START_FUNC_RET);
out:
mutex_unlock(&ftrace_lock);
@@ -3842,7 +3842,7 @@ void unregister_ftrace_graph(void)
ftrace_graph_active--;
ftrace_graph_return = (trace_func_graph_ret_t)ftrace_stub;
ftrace_graph_entry = ftrace_graph_entry_stub;
- ftrace_shutdown(FTRACE_STOP_FUNC_RET);
+ ftrace_shutdown(&global_ops, FTRACE_STOP_FUNC_RET);
unregister_pm_notifier(&ftrace_suspend_notifier);
unregister_trace_sched_switch(ftrace_graph_probe_sched_switch, NULL);
--
1.7.4.4
next prev parent reply other threads:[~2011-05-19 2:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 2:11 [PATCH 00/13] [GIT PULL] ftrace: Allow function tracer to be used by multiple clients Steven Rostedt
2011-05-19 2:11 ` [PATCH 01/13] ftrace: Replace FTRACE_FL_NOTRACE flag with a hash of ignored Steven Rostedt
2011-05-19 2:11 ` [PATCH 02/13] ftrace: Use hash instead for FTRACE_FL_FILTER Steven Rostedt
2011-05-19 2:11 ` [PATCH 03/13] ftrace: Create a global_ops to hold the filter and notrace hashes Steven Rostedt
2011-05-19 2:11 ` [PATCH 04/13] ftrace: Separate hash allocation and assignment Steven Rostedt
2011-05-19 2:11 ` [PATCH 05/13] ftrace: Use counters to enable functions to trace Steven Rostedt
2011-05-19 2:11 ` [PATCH 06/13] ftrace: Add enabled_functions file Steven Rostedt
2011-05-19 2:11 ` Steven Rostedt [this message]
2011-05-19 2:11 ` [PATCH 08/13] ftrace: Have global_ops store the functions that are to be traced Steven Rostedt
2011-05-19 2:12 ` [PATCH 09/13] ftrace: Free hash with call_rcu_sched() Steven Rostedt
2011-05-19 2:12 ` [PATCH 10/13] ftrace: Implement separate user function filtering Steven Rostedt
2011-05-19 2:12 ` [PATCH 11/13] ftrace: Allow dynamically allocated function tracers Steven Rostedt
2011-05-19 2:12 ` [PATCH 12/13] ftrace: Modify ftrace_set_filter/notrace to take ops Steven Rostedt
2011-05-19 2:12 ` [PATCH 13/13] ftrace: Add self-tests for multiple function trace users Steven Rostedt
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=20110519021256.229981824@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome