[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B845668.5090803@redhat.com>
Date: Tue, 23 Feb 2010 17:27:52 -0500
From: Masami Hiramatsu <mhiramat@...hat.com>
To: rostedt@...dmis.org
CC: Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...e.hu>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
lkml <linux-kernel@...r.kernel.org>,
Jim Keniston <jkenisto@...ibm.com>,
Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
Christoph Hellwig <hch@...radead.org>,
"H. Peter Anvin" <hpa@...or.com>,
Anders Kaseorg <andersk@...lice.com>,
Tim Abbott <tabbott@...lice.com>,
Andi Kleen <andi@...stfloor.org>,
Jason Baron <jbaron@...hat.com>,
Mathieu Desnoyers <compudj@...stal.dyndns.org>,
systemtap <systemtap@...rces.redhat.com>,
DLE <dle-develop@...ts.sourceforge.net>
Subject: Re: [PATCH -tip v10 0/9] kprobes: Kprobes jump optimization support
Steven Rostedt wrote:
> On Thu, 2010-02-18 at 17:12 -0500, Masami Hiramatsu wrote:
>
>> This version of patch series uses text_poke_smp() which
>> update kernel text by stop_machine(). That is 'officially'
>> supported on Intel's processors. text_poke_smp() can't
>> be used for modifying NMI code,
>
> But it can be made to use with NMI code. If you look at what I did to
> allow ftrace to modify NMI code, it may be able to do the same thing.
Yeah, I know. But basically, kprobes doesn't support probing NMI.
Maybe, it's possibly the next step. :)
Thank you,
--
Masami Hiramatsu
e-mail: mhiramat@...hat.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