From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] tracing/function-graph-tracer: signal interrupt triggering on output
Date: Tue, 09 Dec 2008 23:56:23 +0100 [thread overview]
Message-ID: <493EF797.7090603@gmail.com> (raw)
In-Reply-To: <493EF64D.50804@gmail.com>
Frederic Weisbecker wrote:
> This patchset adds all the features to draw hardirq triggering on output
> for the function graph tracer.
> An example is given on the third patch.
>
> Just one question, on recordmcount.pl:
>
> my %text_sections = (
> ".text" => 1,
> ".sched.text" => 1,
> ".spinlock.text" => 1,
>
> The .sched.text section is included inside .text, it's a subsection, I'm not sure
> it's necessary to add it in text_sections. In doubt I added the new .irqentry.text
>
> The stat of the patchset:
>
> arch/x86/kernel/apic.c | 3 +-
> arch/x86/kernel/irq_64.c | 3 +-
> arch/x86/kernel/vmlinux_64.lds.S | 1 +
> include/asm-generic/vmlinux.lds.h | 10 +++++
> include/linux/ftrace.h | 11 ++++++
> kernel/trace/trace_functions_graph.c | 66 +++++++++++++++++++++++++++++++--
> scripts/recordmcount.pl | 1 +
> 7 files changed, 89 insertions(+), 6 deletions(-)
>
>
Sorry, forgot to cc LKML on this one.
next parent reply other threads:[~2008-12-09 23:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <493EF64D.50804@gmail.com>
2008-12-09 22:56 ` Frederic Weisbecker [this message]
2008-12-12 10:14 ` [PATCH 0/3] tracing/function-graph-tracer: signal interrupt triggering on output Ingo Molnar
2008-12-12 11:27 ` Frédéric Weisbecker
2008-12-13 7:49 ` Ingo Molnar
2008-12-13 14:26 ` Frédéric Weisbecker
2008-12-13 15:22 ` Frédéric Weisbecker
2008-12-16 23:09 ` Ingo Molnar
2008-12-15 8:03 ` Peter Zijlstra
2008-12-10 2:14 ` Steven Rostedt
2008-12-10 8:46 ` Frédéric Weisbecker
2008-12-10 8:50 ` Wang Liming
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=493EF797.7090603@gmail.com \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--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