[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1324322868.5916.40.camel@gandalf.stny.rr.com>
Date: Mon, 19 Dec 2011 14:27:48 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Jiri Olsa <jolsa@...hat.com>
Cc: fweisbec@...il.com, mingo@...hat.com, paulus@...ba.org,
acme@...stprotocols.net, a.p.zijlstra@...llo.nl,
linux-kernel@...r.kernel.org, aarapov@...hat.com
Subject: Re: [PATCHv2 10/10] ftrace, graph: Add global_ops filter callback
for graph tracing
On Mon, 2011-12-05 at 18:22 +0100, Jiri Olsa wrote:
> The function graph tracer should depend on the global_ops filter,
> and process only functions that pass the global_ops filter.
>
> Currently the function graph tracer gets all the functions
> enabled for tracing no matter what ftrace_ops enabled them.
>
> Adding a hook for the graph entry callback, which ensures the
> function is compared against the global_ops filter and bail
> out of if it does not match.
>
> This hook is enabled only if there's at least one non global
> ftrace_ops registered.
Sorry, I don't like this fix. Right now just let function graph tracer
act weird. If we put in this workaround, it would let us be lazy and not
work on function graph for a proper fix.
The function graph code needs a overhaul anyway. A proper fix may
require fixes in the arch code where the assembly is, as well as a bit
of rewriting of the original code.
This is on my todo list, although it is a bit low priority now. With
this patch set coming in, I can up the priority on the real fix. So
please remove this patch, but keep pinging me to fix it for real ;)
-- Steve
--
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