public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2 v2] tracing/function-graph-tracer: various fixes and features
Date: Fri, 23 Jan 2009 11:19:49 +0100	[thread overview]
Message-ID: <20090123101949.GD15188@elte.hu> (raw)
In-Reply-To: <497917b5.09cc660a.5f4c.ffffc568@mx.google.com>


* Frederic Weisbecker <fweisbec@gmail.com> wrote:

> 
> This patch brings various bugfixes:
> 
> _ Drop the first irrelevant task switch on the very beginning of a trace.
> _ Drop the OVERHEAD word from the headers, the DURATION word is sufficient and will not
>   overlap other columns.
> _ Make the headers fit well their respective columns whatever the selected options.

> About features, one can now disable the duration (this will hide the 
> overhead too for convenient reasons and because on doesn't need overhead 
> if it hasn't the duration

very nice! I've applied this to tip/tracing/function-graph-tracer, thanks 
Frederic!

this:

> I guess no one needs the nanosec precision here, the main goal is to 
> find when happened the events on a cpu when the trace switches from one 
> cpu to another.
> 
> ie:
> 
>   274.874760 |   1)   0.676 us    |      _spin_unlock();
>   274.874762 |   1)   0.609 us    |      native_load_sp0();
>   274.874763 |   1)   0.602 us    |      native_load_tls();
>   274.878739 |   0)   0.722 us    |                  }
>   274.878740 |   0)   0.714 us    |                  native_pmd_val();
>   274.878741 |   0)   0.730 us    |                  native_pmd_val();
> 
> Here there is a 4000 usecs difference when we switch the cpu.

Still needs a solution - if we do cross-CPU traces we want to have a 
global trace clock with 'seemless' transition between CPUs.

	Ingo

  reply	other threads:[~2009-01-23 10:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23  1:04 [PATCH 1/2 v2] tracing/function-graph-tracer: various fixes and features Frederic Weisbecker
2009-01-23 10:19 ` Ingo Molnar [this message]
2009-01-23 10:36   ` Frédéric Weisbecker
2009-01-23 11:00     ` Ingo Molnar
2009-01-23 14:53       ` Steven Rostedt
2009-01-24 16:02       ` Frederic Weisbecker
2009-01-26 14:55         ` 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=20090123101949.GD15188@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