From: Masami Hiramatsu <mhiramat@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH] ftrace: trigger: Call traceoff trigger after event recorded
Date: Fri, 23 Sep 2016 22:11:33 +0900 [thread overview]
Message-ID: <20160923221133.6ddd77b307900a02b6f15b71@kernel.org> (raw)
In-Reply-To: <147335074530.12462.4526186083406015005.stgit@devbox>
Ping?
On Fri, 9 Sep 2016 01:05:45 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> Call traceoff trigger after the event is recorded.
> Since current traceoff trigger is called before recording
> the event, we can not know when the trace is off by what event.
>
> Typical usecase of traceoff/traceon trigger is tracing
> function calls and trace events between a pair of events.
> For example, trace function calls between syscall entry/exit.
> In that case, it is useful if we can see the return code
> of the target syscall.
>
> Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
> ---
> kernel/trace/trace_events_trigger.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/trace/trace_events_trigger.c b/kernel/trace/trace_events_trigger.c
> index a975571..6721a1e8 100644
> --- a/kernel/trace/trace_events_trigger.c
> +++ b/kernel/trace/trace_events_trigger.c
> @@ -1028,6 +1028,7 @@ static struct event_command trigger_traceon_cmd = {
> static struct event_command trigger_traceoff_cmd = {
> .name = "traceoff",
> .trigger_type = ETT_TRACE_ONOFF,
> + .flags = EVENT_CMD_FL_POST_TRIGGER,
> .func = event_trigger_callback,
> .reg = register_trigger,
> .unreg = unregister_trigger,
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2016-09-23 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 16:05 [PATCH] ftrace: trigger: Call traceoff trigger after event recorded Masami Hiramatsu
2016-09-23 13:11 ` Masami Hiramatsu [this message]
2016-09-23 13:34 ` 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=20160923221133.6ddd77b307900a02b6f15b71@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).