Messages in this thread | | | Date | Thu, 13 Nov 2008 00:35:44 +0100 | From | "Frédéric Weisbecker" <> | Subject | Re: [PATCH 2/2] tracing/function-return-tracer: Call prepare_ftrace_return by registers |
| |
2008/11/13 Steven Rostedt <rostedt@goodmis.org>: > > On Wed, 12 Nov 2008, Fr?d?ric Weisbecker wrote: > >> 2008/11/12 Ingo Molnar <mingo@elte.hu>: >> > >> > btw., should we now rename it all to the function-cost tracer? >> >> Yes. I'm preparing a patch to do these renames.... > > I still need to look deeper at your patch set, but what about > "ftrace-exit"? Perhaps in the future this could be used by other tracers > to record exiting of a function.
Hmm... The whole thing is splitted in two levels: the infrastructure to trace on call and return (and call a return handler) and the higher level tracer. The first could be called ftrace_exit because it is waht it does. And the second is much more about cost evaluation of functions and so could be named function_cost. Its functions and structures could have this in their name whereas the low level things could have ftrace_exit in their name.
What do you think?
| |