From: Arjan van de Ven <arjan@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Frédéric Weisbecker" <fweisbec@gmail.com>,
"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 10:29:13 -0700 [thread overview]
Message-ID: <20081027102913.33c51ba6@infradead.org> (raw)
In-Reply-To: <20081027102757.GK8116@elte.hu>
On Mon, 27 Oct 2008 11:27:57 +0100
Ingo Molnar <mingo@elte.hu> wrote:
>
> * Frédéric Weisbecker <fweisbec@gmail.com> wrote:
>
> > 2008/10/27 Ingo Molnar <mingo@elte.hu>:
> > > nice! Applied it to tip/tracing/ftrace. I've added Steve's
> > > Acked-by,
> >
> >
> > Thanks!
> >
> >
> > > 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)
> >
> >
> > Good idea, for example bootgraph.pl matches the case, if Arjan
> > agrees.
>
bootgraph.pl is sort of borderline since it also works without tracing
but I'm not opposed to it if it makes scripts/ more organized
prev parent reply other threads:[~2008-10-27 17:29 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
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 [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=20081027102913.33c51ba6@infradead.org \
--to=arjan@infradead.org \
--cc=fweisbec@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.