[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FCCA8E7.5070407@hitachi.com>
Date: Mon, 04 Jun 2012 21:24:07 +0900
From: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
"Frank Ch. Eigler" <fche@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Frederic Weisbecker <fweisbec@...il.com>,
yrl.pp-manager.tt@...achi.com
Subject: Re: [RFC PATCH -tip 0/9]ftrace, kprobes: Ftrace-based kprobe optimization
(2012/06/04 21:07), Steven Rostedt wrote:
> On Mon, 2012-06-04 at 20:45 +0900, Masami Hiramatsu wrote:
>> I think if I just register kprobe's ftrace_ops without start
>> tracing, I think we can just do tracing without "notrace".
>
> You should be able to register the filter first, and then register
> function tracer. If you register without setting the filter, you will
> start tracing all functions.
>
> I think that may be the problem you are seeing. You want to register the
> filter first and then the ftrace_ops.
Ah, that's all what I need to know! :)
OK, I'll do that for avoiding recursion problem.
Thanks!
--
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@...achi.com
--
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