From: Steven Rostedt <rostedt@goodmis.org>
To: Josh Triplett <josh@joshtriplett.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] ftrace: Add vim script to enable folding for function_graph traces
Date: Thu, 6 Aug 2009 20:04:38 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0908062004170.2840@gandalf.stny.rr.com> (raw)
In-Reply-To: <20090806145701.GB7661@feather>
On Thu, 6 Aug 2009, Josh Triplett wrote:
> function_graph traces look like nested function calls, complete with
> braces denoting the start and end of functions. function-graph-fold.vim
> teaches vim how to fold these functions, to make it more convenient to
> browse them.
>
> To use, :source function-graph-fold.vim while viewing a function_graph
> trace, or use "view -S function-graph-fold.vim some-trace" to load it
> from the command-line together with a trace. You can then use the usual
> vim fold commands, such as "za", to open and close nested functions.
> While closed, a fold will show the total time taken for a call, as would
> normally appear on the line with the closing brace. Folded functions
> will not include finish_task_switch(), so folding should remain
> relatively sane even through a context switch.
>
> Note that this will almost certainly only work well with a single-CPU
> trace (e.g. trace-cmd report --cpu 1). It also takes some time to run
> (a few seconds for a large trace on my laptop). Nevertheless, I found
> it very handy to get an overview of a trace and then drill down on
> problematic calls.
>
> Signed-off-by: Josh Triplett <josh@joshtriplett.org>
Thanks Josh,
I queued it up for 32.
-- Steve
next prev parent reply other threads:[~2009-08-07 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 14:57 [PATCH] ftrace: Add vim script to enable folding for function_graph traces Josh Triplett
2009-08-07 0:04 ` Steven Rostedt [this message]
2009-08-26 7:22 ` [tip:tracing/core] tracing: " tip-bot for Josh Triplett
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=alpine.DEB.2.00.0908062004170.2840@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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;
as well as URLs for NNTP newsgroup(s).