From: Steven Rostedt <rostedt@goodmis.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: fweisbec@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] trace: funcgraph tracer - adding funcgraph-irq option
Date: Thu, 22 Jul 2010 16:00:21 -0400 [thread overview]
Message-ID: <1279828821.3319.23.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1278951670-8133-1-git-send-email-jolsa@redhat.com>
On Mon, 2010-07-12 at 18:21 +0200, Jiri Olsa wrote:
> +/*
> + * Entry check for irq code
> + *
> + * returns 1 if
> + * - we are inside irq code
> + * - we just extered irq code
> + *
> + * retunns 0 if
> + * - funcgraph-interrupts option is set
> + * - we are not inside irq code
> + */
> +static int
> +check_irq_entry(struct trace_iterator *iter, u32 flags, unsigned long addr)
> +{
> + struct fgraph_data *data = iter->private;
> + int cpu = iter->cpu;
> + unsigned long *irq_entry_addr;
> +
> + if (flags & TRACE_GRAPH_PRINT_IRQS)
> + return 0;
> +
> + /*
> + * We are inside the irq code
> + */
> + irq_entry_addr = &(per_cpu_ptr(data->cpu_data, cpu)->irq_entry_addr);
> + if (*irq_entry_addr)
> + return 1;
> +
> + if ((addr < (unsigned long)__irqentry_text_start) ||
> + (addr >= (unsigned long)__irqentry_text_end))
> + return 0;
> +
> + /*
> + * We are entering irq code.
> + */
> + *irq_entry_addr = addr;
> + return 1;
> +}
> +
> +/*
> + * Return check for irq code
> + *
> + * returns 1 if
> + * - we are inside irq code
> + * - we just left irq code
> + *
> + * returns 0 if
> + * - funcgraph-interrupts option is set
> + * - we are not inside irq code
> + */
> +static int
> +check_irq_return(struct trace_iterator *iter, u32 flags, unsigned long addr)
> +{
> + struct fgraph_data *data = iter->private;
> + int cpu = iter->cpu;
> + unsigned long *irq_entry_addr;
> +
> + if (flags & TRACE_GRAPH_PRINT_IRQS)
> + return 0;
> +
> + /*
> + * We are not inside the irq code.
> + */
> + irq_entry_addr = &(per_cpu_ptr(data->cpu_data, cpu)->irq_entry_addr);
> + if (!(*irq_entry_addr))
> + return 0;
> +
> + /*
> + * We are inside the irq code, and this is not the entry.
> + */
> + if (*irq_entry_addr != addr)
> + return 1;
> +
> + /*
> + * We are inside the irq code, and this is returning entry.
> + * Let's not trace it and clear the entry address, since
> + * we are out of irq code.
> + */
> + *irq_entry_addr = 0;
> + return 1;
> +}
> +
> static enum print_line_t
> print_graph_entry(struct ftrace_graph_ent_entry *field, struct trace_seq *s,
> struct trace_iterator *iter, u32 flags)
> @@ -857,6 +943,9 @@ print_graph_entry(struct ftrace_graph_ent_entry *field, struct trace_seq *s,
> static enum print_line_t ret;
> int cpu = iter->cpu;
>
> + if (check_irq_entry(iter, flags, call->func))
> + return TRACE_TYPE_HANDLED;
> +
> if (print_graph_prologue(iter, s, TRACE_GRAPH_ENT, call->func, flags))
> return TRACE_TYPE_PARTIAL_LINE;
>
> @@ -894,6 +983,9 @@ print_graph_return(struct ftrace_graph_ret *trace, struct trace_seq *s,
> int ret;
> int i;
>
> + if (check_irq_return(iter, flags, trace->func))
> + return TRACE_TYPE_HANDLED;
What happens if we lose the return event? That is, due to buffer
overruns, the return of the trace is lost. Then we lose out on all
events until another event of the same IRQ happens and its return is not
lost.
You should save the depth instead of the function. When you are in a
interrupt, record the depth. Then when the depth is less than or equal
to the recorded depth you can restart printing. This may still suffer
from missed returns, but it would not have as much of a consequence when
it happens.
-- Steve
> +
> if (data) {
> struct fgraph_cpu_data *cpu_data;
> int cpu = iter->cpu;
next prev parent reply other threads:[~2010-07-22 20:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 16:21 Jiri Olsa
2010-07-22 20:00 ` Steven Rostedt [this message]
2010-07-23 13:19 ` [PATCHv2] " Jiri Olsa
[not found] ` <20100907113102.GA1912@jolsa.brq.redhat.com>
[not found] ` <1283867057.5133.75.camel@gandalf.stny.rr.com>
2010-09-07 14:53 ` Jiri Olsa
2010-09-15 8:41 ` [tip:perf/core] tracing: Add funcgraph-irq option for function graph tracer tip-bot for Jiri Olsa
2010-09-07 16:28 ` [PATCHv2] trace: funcgraph tracer - adding funcgraph-irq option Steven Rostedt
2010-09-07 17:19 ` Johannes Weiner
2010-09-09 14:44 ` Johannes Weiner
2010-09-09 18:10 ` Jiri Olsa
2010-09-11 1:18 ` 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=1279828821.3319.23.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.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®