From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Tom Zanussi <tom.zanussi@linux.intel.com>, rostedt@goodmis.org
Cc: daniel.wagner@bmw-carit.de, namhyung@kernel.org,
josh@joshtriplett.org, andi@firstfloor.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/10] tracing: Update cond flag when enabling or disabling a trigger
Date: Thu, 21 May 2015 16:21:14 +0900 [thread overview]
Message-ID: <555D876A.7020200@hitachi.com> (raw)
In-Reply-To: <e35ab1173aaa0cf93728a707ee4d987ebc405bb6.1432151408.git.tom.zanussi@linux.intel.com>
On 2015/05/21 6:19, Tom Zanussi wrote:
> When a trigger is enabled, the cond flag should be set beforehand,
> otherwise a trigger that's expecting to process a trace record
> (e.g. one with post_trigger set) could be invoked without one.
>
> Likewise a trigger's cond flag should be reset after it's disabled,
> not before.
>
> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
> Signed-off-by: Daniel Wagner <daniel.wagner@bmw-carit.de>
Reviewed-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Thank you!
> ---
> kernel/trace/trace_events_trigger.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/trace/trace_events_trigger.c b/kernel/trace/trace_events_trigger.c
> index 8712df9..51e2664 100644
> --- a/kernel/trace/trace_events_trigger.c
> +++ b/kernel/trace/trace_events_trigger.c
> @@ -543,11 +543,12 @@ static int register_trigger(char *glob, struct event_trigger_ops *ops,
> list_add_rcu(&data->list, &file->triggers);
> ret++;
>
> + update_cond_flag(file);
> if (trace_event_trigger_enable_disable(file, 1) < 0) {
> list_del_rcu(&data->list);
> + update_cond_flag(file);
> ret--;
> }
> - update_cond_flag(file);
> out:
> return ret;
> }
> @@ -575,8 +576,8 @@ static void unregister_trigger(char *glob, struct event_trigger_ops *ops,
> if (data->cmd_ops->trigger_type == test->cmd_ops->trigger_type) {
> unregistered = true;
> list_del_rcu(&data->list);
> - update_cond_flag(file);
> trace_event_trigger_enable_disable(file, 0);
> + update_cond_flag(file);
> break;
> }
> }
> @@ -1319,11 +1320,12 @@ static int event_enable_register_trigger(char *glob,
> list_add_rcu(&data->list, &file->triggers);
> ret++;
>
> + update_cond_flag(file);
> if (trace_event_trigger_enable_disable(file, 1) < 0) {
> list_del_rcu(&data->list);
> + update_cond_flag(file);
> ret--;
> }
> - update_cond_flag(file);
> out:
> return ret;
> }
> @@ -1344,8 +1346,8 @@ static void event_enable_unregister_trigger(char *glob,
> (enable_data->file == test_enable_data->file)) {
> unregistered = true;
> list_del_rcu(&data->list);
> - update_cond_flag(file);
> trace_event_trigger_enable_disable(file, 0);
> + update_cond_flag(file);
> break;
> }
> }
>
--
Masami HIRAMATSU
Linux Technology Research Center, System Productivity Research Dept.
Center for Technology Innovation - Systems Engineering
Hitachi, Ltd., Research & Development Group
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2015-05-21 7:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 21:19 [PATCH v5 00/10] tracing: 'hist' triggers Tom Zanussi
2015-05-20 21:19 ` [PATCH 01/10] tracing: Update cond flag when enabling or disabling a trigger Tom Zanussi
2015-05-21 7:21 ` Masami Hiramatsu [this message]
2015-05-20 21:19 ` [PATCH v5 02/10] tracing: Make ftrace_event_field checking functions available Tom Zanussi
2015-05-20 21:19 ` [PATCH v5 03/10] tracing: Add event record param to trigger_ops.func() Tom Zanussi
2015-05-20 21:19 ` [PATCH v5 04/10] tracing: Add get_syscall_name() Tom Zanussi
2015-05-20 21:19 ` [PATCH v5 05/10] tracing: Add a per-event-trigger 'paused' field Tom Zanussi
2015-05-20 21:19 ` [PATCH v5 06/10] trace: Add lock-free tracing_map Tom Zanussi
2015-05-20 21:19 ` [PATCH v5 07/10] tracing: Add 'hist' event trigger command Tom Zanussi
2015-05-20 21:19 ` [PATCH v5 08/10] tracing: Add enable_hist/disable_hist triggers Tom Zanussi
2015-05-20 21:19 ` [PATCH v5 09/10] tracing: Add 'hist' trigger Documentation Tom Zanussi
2015-05-20 21:19 ` [PATCH 10/10][RFC] ftrace: Add function_hist tracer Tom Zanussi
2015-05-21 8:08 ` [PATCH v5 00/10] tracing: 'hist' triggers Masami Hiramatsu
2015-05-21 15:26 ` Tom Zanussi
2015-05-21 21:50 ` Masami Hiramatsu
2015-05-21 13:55 ` Steven Rostedt
2015-05-21 14:29 ` Tom Zanussi
2015-05-21 14:31 ` Steven Rostedt
2015-05-21 14:37 ` Tom Zanussi
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=555D876A.7020200@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=andi@firstfloor.org \
--cc=daniel.wagner@bmw-carit.de \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tom.zanussi@linux.intel.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