Messages in this thread | | | Date | Fri, 16 Jan 2009 17:30:21 +0100 | From | Ingo Molnar <> | Subject | Re: [PATCH 0/2] ftrace: updates to tip |
| |
* Steven Rostedt <rostedt@goodmis.org> wrote:
> On Fri, 16 Jan 2009, Ingo Molnar wrote: > > * Steven Rostedt <rostedt@goodmis.org> wrote: > > > > [...] We can register a function to be traced via the function pointer, > > > and we can pick which functions to trace, but we can not separate out > > > different functions for different traces. > > > > Why not? We could have a hash of all traced functions with metadata > > attached. Since patching functions in/out would be a relatively rare > > operation, this would be a highly efficient read-mostly hash. > > I was afraid you would say that :-) > > Yes, we could add something to do this. It would take some thought on a > good api, and implementation. This is not an easy task by any means. We > need a way to map between a function call and a tracer, where a function > call can call more than one tracer.
Note that some other things could be consolidated under per function metadata: for example set_graph_function - which really is a per function attribute too. Plus a lot of new things would be enabled i think.
Ingo
| |