From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] tracing/function-graph-tracer: signal interrupts entry/exit points on outpout
Date: Mon, 8 Dec 2008 13:22:21 +0100 [thread overview]
Message-ID: <20081208122221.GA16560@elte.hu> (raw)
In-Reply-To: <493C7058.4060709@gmail.com>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> +/* Used during output to find the interrupts entry/exit points */
> +const char *ftrace_graph_irq_entries[] = {
> + "smp_call_function_single_interrupt",
> + "xen_call_function_single_interrupt",
> + "wrapper_smp_local_timer_interrupt",
> + "smp_irq_move_cleanup_interrupt",
> + "smp_call_function_interrupt",
> + "xen_call_function_interrupt",
> + "smp_apic_timer_interrupt",
> + "uv_bau_message_interrupt",
> + "mce_threshold_interrupt",
> + "smp_spurious_interrupt",
> + "smp_thermal_interrupt",
> + "smp_error_interrupt",
> + "do_IRQ",
> + NULL
hm, couldnt we move these symbols to a separate section, and then only
check for [section.start ... section.end] instead of this ugly and slow
array?
Missing a few annotations initially is no big deal - we wont have
pretty-print. do_IRQ() and smp_apic_timer_interrupt is what matters most
in practice. "__irqentry" section annotation or so, which puts them into
.text.irqentry or so - and then irqentry_start/end are extracted via
appropriate glue in the arch/x86/kernel/vmlinux* linker script.
Ingo
next prev parent reply other threads:[~2008-12-08 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 0:54 Frederic Weisbecker
2008-12-08 6:19 ` Peter Zijlstra
2008-12-08 13:38 ` Frédéric Weisbecker
2008-12-08 13:47 ` Ingo Molnar
2008-12-08 13:51 ` Frédéric Weisbecker
2008-12-08 12:22 ` Ingo Molnar [this message]
2008-12-08 13:47 ` Frédéric Weisbecker
2008-12-08 14:03 ` 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=20081208122221.GA16560@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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®