From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Tim Bird <tim.bird@am.sony.com>
Subject: Re: [PATCH][GIT PULL] ftrace: Add function names to dangling } in function graph tracer
Date: Sat, 27 Feb 2010 11:04:18 +0100 [thread overview]
Message-ID: <20100227100417.GC5130@nowhere> (raw)
In-Reply-To: <20100227094301.GC31794@elte.hu>
On Sat, Feb 27, 2010 at 10:43:01AM +0100, Ingo Molnar wrote:
> > [tracing] cat trace
> > # tracer: function_graph
> > #
> > # CPU DURATION FUNCTION CALLS
> > # | | | | | | |
> > 0) + 91.897 us | } (irq_exit)
> > 0) ! 567.961 us | } (smp_apic_timer_interrupt)
> > 0) <========== |
> > 0) ! 579.083 us | _raw_spin_lock_irqsave();
> > 0) 4.694 us | _raw_spin_unlock_irqrestore();
> > 0) ! 594.862 us | } (add_wait_queue)
> > 0) ! 603.361 us | } (__pollwait)
> > 0) ! 613.574 us | } (tcp_poll)
> > 0) ! 623.554 us | } (sock_poll)
> > 0) 3.653 us | fget_light();
> > 0) | sock_poll() {
>
> Neat! I think it would read even more C-ish if it was something non-syntactic,
> like:
>
> > 0) ! 594.862 us | } /* add_wait_queue */
> > 0) ! 603.361 us | } /* __pollwait */
> > 0) ! 613.574 us | } /* tcp_poll */
> > 0) ! 623.554 us | } /* sock_poll */
>
> hm?
Agreed. It won't even be confusing with other events that are
printed as comments, since we have the closing brace before.
>
> Ingo
next prev parent reply other threads:[~2010-02-27 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 0:27 [PATCH][GIT PULL] ftrace: Add function names to dangling } in function graph tracer Steven Rostedt
2010-02-27 9:43 ` Ingo Molnar
2010-02-27 10:04 ` Frederic Weisbecker [this message]
2010-02-27 19:19 ` Steven Rostedt
2010-02-27 10:02 ` Frederic Weisbecker
2010-02-27 19:25 ` Steven Rostedt
2010-02-28 18:16 ` Frederic Weisbecker
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=20100227100417.GC5130@nowhere \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tim.bird@am.sony.com \
/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