Message-ID: <1338331514.13348.298.camel@gandalf.stny.rr.com>
Subject: Re: [RFC PATCH -tip  0/9]ftrace, kprobes: Ftrace-based kprobe
 optimization
From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
        Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
        "Frank Ch. Eigler" <fche@redhat.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        Frederic Weisbecker <fweisbec@gmail.com>,
        yrl.pp-manager.tt@hitachi.com
Date: Tue, 29 May 2012 18:45:14 -0400
In-Reply-To: <20120529124833.9191.23007.stgit@localhost.localdomain>
References: <20120529124833.9191.23007.stgit@localhost.localdomain>
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 905
Lines: 22

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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/