[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49C9470F.8090202@am.sony.com>
Date: Tue, 24 Mar 2009 13:48:15 -0700
From: Tim Bird <tim.bird@...sony.com>
To: Ingo Molnar <mingo@...e.hu>
CC: Frédéric Weisbecker <fweisbec@...il.com>,
linux-arm-kernel <linux-arm-kernel@...ts.arm.linux.org.uk>,
linux kernel <linux-kernel@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>,
Abhishek Sagar <sagar.abhishek@...il.com>,
Russell King <rmk@....linux.org.uk>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
Subject: Re: Anyone working on ftrace function graph support on ARM?
Ingo Molnar wrote:
> * Tim Bird <tim.bird@...sony.com> wrote:
>
>> My ultimate goal is to add function duration filtering, which is
>> one of the nicer features of KFT (an older tracer I used to
>> maintain out-of-mainline). With all the ftrace and ringbuffer
>> support already in mainline, this shouldn't be too hard, but I
>> need to start with basic graph support on ARM first.
>
> ah, function duration filtering - is that to only show functions
> which have a duration beyond a certain (runtime configurable) value?
Exactly. With KFT, you set a "mintime filter", and it removed from
the trace buffer any functions which were less than the threshhold.
This was not high cost, because you usually only removed the most
recently added function in the trace buffer.
This lets you focus on routines that last a long time. I used
it mainly to find long-duration routines in early boot.
The initcall tracer serves a similar purpose, but not at the
same granularity.
It greatly extends the length of time you can trace, before the
buffer fills up.
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================
--
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/
Powered by blists - more mailing lists