From: Frederic Weisbecker <fweisbec@gmail.com>
To: Steven Rostedt <srostedt@redhat.com>
Cc: Tim Bird <tim.bird@am.sony.com>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] ftrace - add support for tracing_thresh to function_graph tracer
Date: Sat, 20 Feb 2010 15:21:04 +0100 [thread overview]
Message-ID: <20100220142054.GA5354@nowhere> (raw)
In-Reply-To: <1265934415.2737.344.camel@localhost.localdomain>
On Thu, Feb 11, 2010 at 07:26:55PM -0500, Steven Rostedt wrote:
> On Thu, 2010-02-11 at 16:01 -0800, Tim Bird wrote:
> > On 02/11/2010 03:10 PM, Steven Rostedt wrote:
> > > On Wed, 2010-02-10 at 14:52 -0800, Tim Bird wrote:
> > >> static struct tracer_opt trace_opts[] = {
> > >> /* Display overruns? (for self-debug purpose) */
> > >> @@ -53,6 +54,8 @@ static struct tracer_opt trace_opts[] = {
> > >> { TRACER_OPT(funcgraph-duration, TRACE_GRAPH_PRINT_DURATION) },
> > >> /* Display absolute time of an entry */
> > >> { TRACER_OPT(funcgraph-abstime, TRACE_GRAPH_PRINT_ABS_TIME) },
> > >> + /* Display function name on exit, instead of just closing brace */
> > >> + { TRACER_OPT(funcgraph-exit, TRACE_GRAPH_PRINT_FUNC_EXIT) },
> > >> { } /* Empty entry */
> > >
> > > I wonder if this should be enabled on start up of the function graph
> > > tracer if the threshold is set?
> > >
> > > Otherwise people will wonder WTF?
> >
> > Indeed. I'm not sure exactly how to do this.
> >
> > Would it be better to set the option when current_tracer
> > is set with 'function_graph', and tracing_thresh is non-zero?
>
> The above is the only one I would do. If tracing_thresh is non-zero when
> the function_graph tracer is set, on the start up code in the function
> tracer (graph_trace_init).
>
> Just enable the option if trace_thresh is set. If you enable function
> graph tracer and have the trace_thresh set, then this type of tracing
> starts immediately. It also keeps the code nicely in the
> trace_function_graph.c file, and does not need to touch the setting of
> tracing_thresh.
Actually why do we encumber with both tracing_thresh and the funcgraph-exit
option?
We could just have the output and the record check tracing_thresh instead
of the funcgraph-exit option.
next prev parent reply other threads:[~2010-02-20 14:21 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 [this message]
2010-02-22 14:48 ` Steven Rostedt
2010-02-22 18:14 ` Frederic Weisbecker
2010-02-20 14:43 ` Frederic Weisbecker
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=20100220142054.GA5354@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