From: Frederic Weisbecker <fweisbec@gmail.com>
To: Tim Bird <tim.bird@am.sony.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>,
Steven Rostedt <srostedt@redhat.com>
Subject: Re: [PATCH 1/1] ftrace - add support for tracing_thresh to function_graph tracer
Date: Sat, 20 Feb 2010 15:43:04 +0100 [thread overview]
Message-ID: <20100220144302.GB5354@nowhere> (raw)
In-Reply-To: <4B7338BF.1070505@am.sony.com>
On Wed, Feb 10, 2010 at 02:52:47PM -0800, Tim Bird wrote:
> int trace_graph_entry(struct ftrace_graph_ent *trace)
> {
> struct trace_array *tr = graph_array;
> @@ -221,6 +226,10 @@ int trace_graph_entry(struct ftrace_graph_ent *trace)
> if (!ftrace_graph_addr(trace->func))
> return 0;
>
> + /* if tracing duration, only save function exits (omit function entries in log) */
> + if (tracing_thresh)
> + return 1;
> +
Instead of having yet another check here, may be should we
have a dedicated stub trace_graph_entry?
> @@ -254,6 +263,10 @@ static void __trace_graph_return(struct trace_array *tr,
> if (unlikely(__this_cpu_read(per_cpu_var(ftrace_cpu_disabled))))
> return;
>
> + if (tracing_thresh &&
> + (trace->rettime - trace->calltime < tracing_thresh))
> + return;
> +
And perhaps we can do the same for the return handler?
We could have a trace_graph_return_threshold that
performs the above check and then relies on trace_graph_return.
Thanks.
next prev parent reply other threads:[~2010-02-20 14:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 22:45 [PATCH 1/1] ftrace - add support for tracing_thresh to function_graph tracer Tim Bird
2010-02-10 22:52 ` Tim Bird
2010-02-11 23:10 ` Steven Rostedt
2010-02-12 0:01 ` Tim Bird
2010-02-12 0:26 ` Steven Rostedt
2010-02-13 3:47 ` Tim Bird
2010-02-13 4:12 ` Steven Rostedt
2010-02-20 14:21 ` Frederic Weisbecker
2010-02-22 14:48 ` Steven Rostedt
2010-02-22 18:14 ` Frederic Weisbecker
2010-02-20 14:43 ` Frederic Weisbecker [this message]
2010-02-22 14:57 ` Steven Rostedt
2010-02-22 18:17 ` Frederic Weisbecker
2010-02-23 1:18 ` Tim Bird
2010-02-23 1:23 ` Steven Rostedt
2010-02-25 15:44 ` 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=20100220144302.GB5354@nowhere \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srostedt@redhat.com \
--cc=tim.bird@am.sony.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