From: Frederic Weisbecker <fweisbec@gmail.com>
To: Tim Bird <tim.bird@am.sony.com>
Cc: "Bird, Tim" <Timothy.Bird@am.sony.com>,
Steven Rostedt <srostedt@redhat.com>,
linux kernel <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] ftrace: add tracing_thresh support to function_graph tracer (v3)
Date: Sat, 27 Feb 2010 11:25:58 +0100 [thread overview]
Message-ID: <20100227102556.GE5130@nowhere> (raw)
In-Reply-To: <4B881291.3040903@am.sony.com>
On Fri, Feb 26, 2010 at 10:27:29AM -0800, Tim Bird wrote:
> On 02/25/2010 06:46 PM, Frederic Weisbecker wrote:
> >> +static int __init set_tracing_thresh(char *str)
> >> +{
> >> + unsigned long threshhold;
> >> + int ret;
> >> +
> >> + if (!str)
> >> + return 0;
> >> + ret = strict_strtoul(str, 0, &threshhold);
> >> + if (ret < 0)
> >> + return 0;
> >> + tracing_thresh = threshhold * 1000;
> >> + return 1;
> >> +}
> >> +__setup("tracing_thresh=", set_tracing_thresh);
> >
> > Looks like setting this, while the function graph tracer (normal
> > mode) is running, will have no effect. That said it's perfectly
> > fine as it would be pointless to change this value in the middle
> > of the tracing.
> >
> The command line is parsed before the tracer is activated, so
> tracing_thresh is set when trace_graph_init() is called, which
> results in the desired behaviour (that is, if you specify the
> tracing_thresh on the command line, you get the duration
> filtering on bootup).
Oh right, I made a confusion with the tracing_thresh file
write callback.
next prev parent reply other threads:[~2010-02-27 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 23:36 [PATCH] ftrace: add tracing_thresh support to function_graph tracer (v3) Tim Bird
2010-02-26 2:46 ` Frederic Weisbecker
2010-02-26 18:27 ` Tim Bird
2010-02-27 10:25 ` Frederic Weisbecker [this message]
2010-02-26 4:37 ` Steven Rostedt
2010-02-26 18:52 ` Tim Bird
2010-02-26 20:37 ` Steven Rostedt
2010-03-11 14:37 ` [tip:tracing/urgent] function-graph: Add tracing_thresh support to function_graph tracer tip-bot for Tim Bird
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=20100227102556.GE5130@nowhere \
--to=fweisbec@gmail.com \
--cc=Timothy.Bird@am.sony.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.