Messages in this thread | | | Subject | Re: [RFC PATCH -tip 0/9]ftrace, kprobes: Ftrace-based kprobe optimization | From | Steven Rostedt <> | Date | Tue, 29 May 2012 18:45:14 -0400 |
| |
On Tue, 2012-05-29 at 21:48 +0900, Masami Hiramatsu wrote:
> Also, this makes all __kprobes functions "notrace", because > some of those functions are considered as to be called from > kprobes handler which is called from function tracer. > I think that is another discussion point. Perhaps, we need > to introduce another tag which means "don't put kprobe on > this function" instead of __kprobes and apply that.
Actually, instead, we can force kprobes to have all "__kprobes" functions added to its 'notrace' ftrace_ops. This will just keep kprobes from function tracing these, as I find myself tracing functions marked by kprobes quite a bit.
-- Steve
| |