From: "Frédéric Weisbecker" <fweisbec@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Steven Rostedt" <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
"Andrew Morton" <akpm@linux-foundation.org>,
"Chris Mason" <chris.mason@oracle.com>
Subject: Re: [PATCH 0/2] ftrace: updates to tip
Date: Fri, 16 Jan 2009 14:08:36 +0100 [thread overview]
Message-ID: <c62985530901160508t318980a5vbbe9198f326e124@mail.gmail.com> (raw)
In-Reply-To: <20090116112345.GC20082@elte.hu>
2009/1/16 Ingo Molnar <mingo@elte.hu>:
>
> * Steven Rostedt <rostedt@goodmis.org> wrote:
>
>> Ingo,
>>
>> The first patch is critical, and needs to stay with trace_output.c Not
>> that critical since trace_output.c is not in mainline yet.
>>
>> The second patch gives the ability to stack trace functions. I've been
>> leery about adding this and still keep it a separate option from the
>> "stacktrace" that already exists. This is because when enabled with no
>> filtering, the lag between typing and seeing what is typed can be up to
>> 10 seconds or more.
>
> Btw., is this true even if frame pointers are enabled? When frame pointers
> are disabled we scan the full kernel stack => that can be quite slow if
> every kernel function is traced ;-)
Hi Ingo,
The function tracer selects Frame pointers :-)
Frederic.
>> I made the function stack trace an option attached to the function
>> tracer, so it must be enabled after the function tracer has been set.
>> This still needs to be updated in ftrace.txt.
>
> maybe we could drive this via the filter API? Something like:
>
> echo "*btrfs*:stacktrace" >> set_filter_functions
>
> Would automatically mean that those functions will all generate
> stacktraces too. Note how safe this API is by default: the filter is used
> for a narrow scope of functions anwyay. To get it for all kernel functions
> one would have to do:
>
> echo "*:stacktrace" >> set_filter_functions
>
> Which one cannot do accidentally.
>
> What do you think?
>
>> The following patches are in:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
>>
>> branch: tip/devel
>>
>>
>> Lai Jiangshan (1):
>> ftrace: fix trace_output
>>
>> Steven Rostedt (1):
>> ftrace: add stack trace to function tracer
>>
>> ----
>> kernel/trace/trace.c | 26 ++++++++----
>> kernel/trace/trace.h | 7 +++
>> kernel/trace/trace_functions.c | 84 ++++++++++++++++++++++++++++++++++++++++
>> kernel/trace/trace_output.c | 65 +++++++++++++++----------------
>> kernel/trace/trace_output.h | 4 +-
>> 5 files changed, 141 insertions(+), 45 deletions(-)
>
> Pulled into tip/tracing/ftrace, thanks Steve!
>
> Ingo
>
next prev parent reply other threads:[~2009-01-16 13:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 0:40 Steven Rostedt
2009-01-16 0:40 ` [PATCH 1/2] ftrace: fix trace_output Steven Rostedt
2009-01-16 1:40 ` Andrew Morton
2009-01-16 1:46 ` Steven Rostedt
2009-01-16 0:40 ` [PATCH 2/2] ftrace: add stack trace to function tracer Steven Rostedt
2009-01-16 0:48 ` Steven Rostedt
2009-01-16 10:08 ` Frédéric Weisbecker
2009-01-16 14:28 ` Steven Rostedt
2009-01-16 11:19 ` Ingo Molnar
2009-01-16 11:23 ` [PATCH 0/2] ftrace: updates to tip Ingo Molnar
2009-01-16 13:08 ` Frédéric Weisbecker [this message]
2009-01-16 13:10 ` Ingo Molnar
2009-01-16 14:32 ` Steven Rostedt
2009-01-16 15:21 ` Ingo Molnar
2009-01-16 15:53 ` Steven Rostedt
2009-01-16 16:02 ` Ingo Molnar
2009-01-16 16:03 ` Ingo Molnar
2009-01-16 16:22 ` Steven Rostedt
2009-01-16 16:30 ` Ingo Molnar
2009-01-16 22:59 ` Ingo Molnar
2009-01-17 1:14 ` Steven Rostedt
2009-01-17 13:48 ` Frederic Weisbecker
2009-01-17 22:34 ` Ingo Molnar
2009-01-18 7:27 ` Ingo Molnar
2009-01-16 21:47 ` Chris Mason
2009-01-16 22:26 ` Ingo Molnar
2009-01-17 1:30 ` Chris Mason
2009-01-17 2:38 ` Arnaldo Carvalho de Melo
2009-01-19 13:31 ` Ingo Molnar
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=c62985530901160508t318980a5vbbe9198f326e124@mail.gmail.com \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
/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
all inboxes | Powered by JetHome®