From: Frederic Weisbecker <fweisbec@gmail.com>
To: Zhaolei <zhaolei@cn.fujitsu.com>
Cc: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
Tom Zanussi <tzanussi@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] ftrace: clean up of using ftrace_event_enable_disable()
Date: Sun, 24 May 2009 22:46:23 +0200 [thread overview]
Message-ID: <20090524204620.GC6471@nowhere> (raw)
In-Reply-To: <4A16791C.8090501@cn.fujitsu.com>
On Fri, May 22, 2009 at 06:06:20PM +0800, Zhaolei wrote:
> Always use tracing_stop_cmdline_record() to enable/disable a event.
>
> Impact: cleanup, no functionality changed
>
> Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
> ---
> kernel/trace/trace_events.c | 44 +++++++++++++-----------------------------
> 1 files changed, 14 insertions(+), 30 deletions(-)
>
> diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
> index df35e5e..16ef47a 100644
> --- a/kernel/trace/trace_events.c
> +++ b/kernel/trace/trace_events.c
> @@ -76,26 +76,9 @@ static void trace_destroy_fields(struct ftrace_event_call *call)
>
> #endif /* CONFIG_MODULES */
>
> -static void ftrace_clear_events(void)
> -{
> - struct ftrace_event_call *call;
> -
> - mutex_lock(&event_mutex);
> - list_for_each_entry(call, &ftrace_events, list) {
Don't we have a "for_each_event" ?
> -
> - if (call->enabled) {
> - call->enabled = 0;
> - tracing_stop_cmdline_record();
> - call->unregfunc();
> - }
> - }
> - mutex_unlock(&event_mutex);
> -}
> -
> static void ftrace_event_enable_disable(struct ftrace_event_call *call,
> int enable)
> {
> -
> switch (enable) {
> case 0:
> if (call->enabled) {
> @@ -114,6 +97,17 @@ static void ftrace_event_enable_disable(struct ftrace_event_call *call,
> }
> }
>
> +static void ftrace_clear_events(void)
> +{
> + struct ftrace_event_call *call;
> +
> + mutex_lock(&event_mutex);
> + list_for_each_entry(call, &ftrace_events, list) {
> + ftrace_event_enable_disable(call, 0);
> + }
> + mutex_unlock(&event_mutex);
> +}
> +
> /*
> * __ftrace_set_clr_event(NULL, NULL, NULL, set) will set/unset all events.
> */
> @@ -1059,11 +1053,7 @@ static void trace_module_remove_events(struct module *mod)
> list_for_each_entry_safe(call, p, &ftrace_events, list) {
> if (call->mod == mod) {
> found = true;
> - if (call->enabled) {
> - call->enabled = 0;
> - tracing_stop_cmdline_record();
> - call->unregfunc();
> - }
> + ftrace_event_enable_disable(call, 0);
> if (call->event)
> unregister_ftrace_event(call->event);
> debugfs_remove_recursive(call->dir);
> @@ -1265,15 +1255,9 @@ static __init void event_trace_self_tests(void)
> continue;
> }
>
> - call->enabled = 1;
> - tracing_start_cmdline_record();
> - call->regfunc();
> -
> + ftrace_event_enable_disable(call, 1);
> event_test_stuff();
> -
> - call->unregfunc();
> - tracing_stop_cmdline_record();
> - call->enabled = 0;
> + ftrace_event_enable_disable(call, 0);
>
> pr_cont("OK\n");
> }
Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
next prev parent reply other threads:[~2009-05-24 20:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 7:08 [PATCH 1/2] ftrace: Add task_comm support for trace_event Zhaolei
2009-05-21 7:09 ` [PATCH 2/2] ftrace: clean up of using ftrace_event_enable_disable() Zhaolei
2009-05-21 13:16 ` Steven Rostedt
2009-05-21 13:15 ` [PATCH 1/2] ftrace: Add task_comm support for trace_event Steven Rostedt
2009-05-22 8:01 ` Ingo Molnar
2009-05-22 8:25 ` Ingo Molnar
2009-05-22 8:49 ` Zhaolei
2009-05-22 10:03 ` [PATCH v2 0/2] " Zhaolei
2009-05-22 10:05 ` [PATCH v2 1/2] " Zhaolei
2009-05-24 20:42 ` Frederic Weisbecker
2009-05-25 3:54 ` Zhaolei
2009-05-25 8:27 ` Frederic Weisbecker
2009-05-22 10:06 ` [PATCH v2 2/2] ftrace: clean up of using ftrace_event_enable_disable() Zhaolei
2009-05-24 20:46 ` Frederic Weisbecker [this message]
2009-05-25 5:34 ` Zhaolei
2009-05-25 8:32 ` Frederic Weisbecker
2009-05-22 11:51 ` [PATCH v2 0/2] ftrace: Add task_comm support for trace_event Ingo Molnar
2009-05-25 8:59 ` Zhaolei
2009-05-25 16:45 ` Frederic Weisbecker
2009-05-25 17:01 ` Frederic Weisbecker
2009-05-25 10:03 ` [PATCH v3 " Zhaolei
2009-05-25 10:11 ` [PATCH v3 1/2] " Zhaolei
2009-05-26 0:44 ` Frederic Weisbecker
2009-05-25 10:13 ` [PATCH v3 2/2] ftrace: clean up of using ftrace_event_enable_disable() Zhaolei
2009-05-23 15:16 ` [PATCH 1/2] ftrace: Add task_comm support for trace_event Christoph Hellwig
2009-05-23 15:18 ` Christoph Hellwig
2009-05-27 22:34 ` [tip:tracing/core] " tip-bot for Zhaolei
2009-05-27 22:35 ` [tip:tracing/core] ftrace: clean up of using ftrace_event_enable_disable() tip-bot for Zhaolei
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=20090524204620.GC6471@nowhere \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tzanussi@gmail.com \
--cc=zhaolei@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).