From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Tim Bird <tim.bird@am.sony.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] tracing/function-graph-tracer: improve duration output
Date: Wed, 03 Dec 2008 02:34:30 +0100 [thread overview]
Message-ID: <4935E226.3060906@gmail.com> (raw)
In-Reply-To: <4935E19C.3090501@gmail.com>
Frederic Weisbecker wrote:
> Impact: better output of duration for long calls
>
> The old duration output didn't exceeded 9999.999 us to fit the column
> and the nanosecs were always 3 numbers. As Ingo suggested, it's better
> to have the whole microseconds elapsed time and shift the nanosecs precision
> if needed to fit the maximum 7 numbers. And usec need more number, the case
> should be rare and important enough to break a bit the column alignment to
> show it.
>
> So, depending of the duration value, we now have these patterns:
>
> u.nnn
> uu.nnn
> uuu.nnn
> uuuu.nnn
> uuuuu.nn
> uuuuuu.n
> uuuuuuuu.....
An example of a trace after these two patches (with funcgraph-proc enabled):
0) cat-2796 | | put_prev_task_fair() {
0) cat-2796 | 0.609 us | update_curr();
0) cat-2796 | 1.842 us | }
0) cat-2796 | | pick_next_task_fair() {
0) cat-2796 | 0.526 us | wakeup_preempt_entity();
0) cat-2796 | 0.797 us | set_next_entity();
0) cat-2796 | 0.541 us | hrtick_start_fair();
0) cat-2796 | 4.195 us | }
0) cat-2796 | 1.263 us | _spin_trylock();
0) cat-2796 | 0.624 us | _spin_unlock();
0) cat-2796 | 0.789 us | _spin_trylock();
0) cat-2796 | 0.617 us | _spin_unlock();
0) cat-2796 | 0.579 us | native_load_sp0();
0) cat-2796 | 0.722 us | native_load_tls();
------------------------------------------
| 0) cat-2796 => events/-9
------------------------------------------
0) events/-9 | | finish_task_switch() {
0) events/-9 | 0.789 us | _spin_unlock_irq();
0) events/-9 | 2.309 us | }
0) events/-9 | ! 269848.5 us | }
0) events/-9 | 0.601 us | finish_wait();
0) events/-9 | 0.662 us | kthread_should_stop();
0) events/-9 | | run_workqueue() {
0) events/-9 | 1.136 us | _spin_lock_irq();
0) events/-9 | 0.918 us | _spin_unlock_irq();
0) events/-9 | | console_callback() {
0) events/-9 | | acquire_console_sem() {
0) events/-9 | | down() {
0) events/-9 | 1.534 us | _spin_lock_irqsave();
0) events/-9 | 0.812 us | _spin_unlock_irqrestore();
0) events/-9 | 4.369 us | }
0) events/-9 | 5.903 us | }
next prev parent reply other threads:[~2008-12-03 1:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 1:32 [PATCH 2/2] tracing/function-graph-tracer: improve duration output Frederic Weisbecker
2008-12-03 1:34 ` Frederic Weisbecker [this message]
2008-12-03 8:19 ` Ingo Molnar
2008-12-03 8:33 ` Ingo Molnar
2008-12-03 10:07 ` Frédéric Weisbecker
2008-12-03 10:21 ` Peter Zijlstra
2008-12-03 10:23 ` Frédéric Weisbecker
2008-12-03 10:27 ` Peter Zijlstra
2008-12-03 10:29 ` Frédéric Weisbecker
2008-12-03 11:52 ` Steven Rostedt
2008-12-03 13:11 ` Frédéric Weisbecker
2008-12-03 13:17 ` Peter Zijlstra
2008-12-03 13:21 ` Steven Rostedt
2008-12-03 15:44 ` Frédéric Weisbecker
2008-12-03 16:31 ` Steven Rostedt
2008-12-03 14:22 ` Ingo Molnar
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=4935E226.3060906@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 \
--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