public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: Steven Rostedt <srostedt@redhat.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 1/1] ftrace - add support for tracing_thresh to function_graph tracer
Date: Thu, 11 Feb 2010 16:01:06 -0800	[thread overview]
Message-ID: <4B749A42.2080703@am.sony.com> (raw)
In-Reply-To: <1265929831.2737.340.camel@localhost.localdomain>

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?
Or should I set the option when tracing_thresh is set to
non-zero, and the current_trace is set to 'function_graph'?

Or both?

It wouldn't automatically reset to nofuncgraph-exit
unless I also put some magic in for that.  I'm
pretty sure that disabling it automatically would
lead to unobvious behaviour for the user.

I'll look into how to access the options
from those two points, and see what looks feasible.
 -- Tim

=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================


  reply	other threads:[~2010-02-12  0:01 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 [this message]
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
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=4B749A42.2080703@am.sony.com \
    --to=tim.bird@am.sony.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srostedt@redhat.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