public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: linux kernel <linux-kernel@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 0/4] ftrace - Add function duration tracer to ftrace
Date: Wed, 9 Dec 2009 14:40:19 -0800	[thread overview]
Message-ID: <4B202753.4010108@am.sony.com> (raw)

I've created a new tracer, called the "function duration" tracer,
which is derived from the existing function graph tracer.  The
new feature of this tracer, relative to the function graph tracer,
is that it allows filtering by duration.

The rationale for creating a separate tracer is that some of the
optimizations used for the duration tracer were incompatible with
the function graph tracer.  Specifically, I avoid superfluous
calls to the ring_buffer code, avoiding substantial overhead
penalties.  Also, this tracer is more suitable for use at
bootup time (I have a set of patches pending which adds support
for that, on ARM).

The output format for the tracer is amenable to grep-ing.
That is, the duration is on the same line as the function name.

For details about this, see my presentation from the Japan Linux
Symposium:
http://elinux.org/images/7/70/Measuring-function-duration-with-ftrace-oct-2009.pdf

with more information available at the elinux wiki page:
http://elinux.org/Ftrace_Function_Graph_ARM

Patches to follow.  Thanks.
 -- Tim



             reply	other threads:[~2009-12-09 22:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 22:40 Tim Bird [this message]
2009-12-10  3:41 ` [PATCH 0/4] ftrace - Add function duration tracer to ftrace Steven Rostedt
2009-12-10 20:21   ` Tim Bird
2009-12-11  2:50     ` Steven Rostedt

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=4B202753.4010108@am.sony.com \
    --to=tim.bird@am.sony.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox