From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RESEND] ftrace: Add a script to produce a hierarchical view of a function trace
Date: Mon, 27 Oct 2008 11:01:48 +0100 [thread overview]
Message-ID: <20081027100148.GB8116@elte.hu> (raw)
In-Reply-To: <490513D5.7080806@gmail.com>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> Ok it's corrected thanks to the trace sent by Steven.
> Here is a V2.
> ---
> From: Frederic Weisbecker <fweisbec@gmail.com>
> Subject: [PATCH] ftrace: Add a script to produce a hierarchical view of a function trace
>
> This script parses a function trace and then produces a hierarchical view of the
> function call stack after processing it into a tree.
>
> Changes on V2:
> _ Support both the files "trace" and "trace_pipe" (comments and space differences)
> _ Correct the mini HOW-TO at the beginning.
>
> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
nice! Applied it to tip/tracing/ftrace. I've added Steve's Acked-by,
and i've moved the script to scripts/tracing/ - now that we'll have a
handful of utility scripts there we might as well separate it a bit
more clearly from the usual body of kernel scripts.
i think we should move the other utility scripts there too. (but not
the recordmcount script - that is an infrastructure script, not a
utility script)
Ingo
next prev parent reply other threads:[~2008-10-27 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 21:20 [PATCH][RESEND] ftrace: Add a script to produce a hierarchical view of a function trace Frederic Weisbecker
2008-10-26 21:28 ` Frédéric Weisbecker
2008-10-26 23:10 ` Steven Rostedt
2008-10-26 23:26 ` Frédéric Weisbecker
2008-10-27 1:05 ` Frederic Weisbecker
2008-10-27 10:01 ` Ingo Molnar [this message]
2008-10-27 10:26 ` Frédéric Weisbecker
2008-10-27 10:27 ` Ingo Molnar
2008-10-27 17:29 ` Arjan van de Ven
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=20081027100148.GB8116@elte.hu \
--to=mingo@elte.hu \
--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