From: Steven Rostedt <rostedt@goodmis.org>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] tracing, function graph: Remove the noisy output when use function graph filter
Date: Thu, 17 Jun 2010 11:55:23 -0400 [thread overview]
Message-ID: <1276790123.3556.111.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <4C19E3C3.2060900@cn.fujitsu.com>
On Thu, 2010-06-17 at 16:58 +0800, Lai Jiangshan wrote:
> If we use function graph filter(echo some_functions >> set_graph_function)
> we are only interested in the graph of some_functions.
>
> But if a interrupt occurs when these functions are being traced(or preparing),
> the graphs of the handlers of this interrupt are also recorded.
> These events that we aren't interested in are totally noisy.
Umm, sorry, I prefer the noise. When analyzing the network stack, I
like to see the interrupts that preempt the code.
What you could do is add an function_graph option that disables it, but
do not make it the default.
>
> This patch remove them(very very seldom noise is still left,
> It's OK for tracing, doesn't it?).
>
> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> ---
> diff --git a/kernel/trace/trace_functions_graph.c b/kernel/trace/trace_functions_graph.c
> index 79f4bac..9c130b3 100644
> --- a/kernel/trace/trace_functions_graph.c
> +++ b/kernel/trace/trace_functions_graph.c
> @@ -12,6 +12,8 @@
> #include <linux/slab.h>
> #include <linux/fs.h>
>
> +#include <asm/irq_regs.h>
> +
> #include "trace.h"
> #include "trace_output.h"
>
> @@ -213,13 +215,19 @@ int trace_graph_entry(struct ftrace_graph_ent *trace)
> int ret;
> int cpu;
> int pc;
> + int depth = trace->depth;
> + unsigned long long cntxt = (unsigned long)(void *)get_irq_regs();
>
> if (!ftrace_trace_task(current))
> return 0;
>
> /* trace it when it is-nested-in or is a function enabled. */
> - if (!(trace->depth || ftrace_graph_addr(trace->func)))
> - return 0;
> + if (!ftrace_graph_addr(trace->func)) {
> + if (!depth || current->ret_stack[depth - 1].subtime != cntxt)
> + return 0;
> + }
This will slow down the tracing when inside the function. You are
testing every function to see if we should show the trace, even when we
are inside a function we are tracing.
> + /* We don't use subtime here, reuse it to save context. */
> + current->ret_stack[depth].subtime = cntxt;
This should then be a union if it is used for two things. That documents
it better.
>
> local_irq_save(flags);
> cpu = raw_smp_processor_id();
If you make the above into an option, then we can have
int no_irqs = tracer_flags.val & TRACE_GRAPH_NO_IRQS;
[...]
if (!(trace->depth || ftrace_graph_addr(trace->func)))
return 0;
if (no_irqs) {
cntx = (unsigned long)(void *)get_irq_regs();
if (trace->depth &&
current->ret_stack[depth - 1].subtime != cntxt)
return 0;
current->ret_stack[depth].subtime = cntxt;
}
Also, I'm not really happy about the double use of subtime. It pevents
the function graph from ever ignoring the time it calls the child
functions.
-- Steve
prev parent reply other threads:[~2010-06-17 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 8:58 Lai Jiangshan
2010-06-17 15:55 ` Steven Rostedt [this message]
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=1276790123.3556.111.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®