linux-kernel - [PATCH 0/4] ftrace - Add function duration tracer to ftrace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4B202753.4010108@am.sony.com>
Date:	Wed, 9 Dec 2009 14:40:19 -0800
From:	Tim Bird <tim.bird@...sony.com>
To:	linux kernel <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Ingo Molnar <mingo@...e.hu>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: [PATCH 0/4] ftrace - Add function duration tracer to ftrace

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/