public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@redhat.com>
To: rostedt@goodmis.org
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@elte.hu>,
	Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Jim Keniston <jkenisto@us.ibm.com>,
	Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
	Christoph Hellwig <hch@infradead.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Anders Kaseorg <andersk@ksplice.com>,
	Tim Abbott <tabbott@ksplice.com>,
	Andi Kleen <andi@firstfloor.org>, Jason Baron <jbaron@redhat.com>,
	Mathieu Desnoyers <compudj@krystal.dyndns.org>,
	systemtap <systemtap@sources.redhat.com>,
	DLE <dle-develop@lists.sourceforge.net>
Subject: Re: [PATCH -tip v10 0/9] kprobes: Kprobes jump optimization support
Date: Wed, 24 Feb 2010 08:41:13 -0500	[thread overview]
Message-ID: <4B852C79.8000702@redhat.com> (raw)
In-Reply-To: <4B845668.5090803@redhat.com>

Masami Hiramatsu wrote:
> 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. :)

I mean that it may be overkill for this series, because the kprobes
itself doesn't support NMI. So I think it should be done by another
series (for simplify patches).


BTW, now there are two candidates for NMI supported text_poke()
on x86. AFAIK, those have following issues/features.

- text_poke_fixup()
  - Send IPI twice instead of kstop_machine.
  - Need a detour buffer if replacing code is not a jump.
  - Unofficial method for x86.

- generic ftrace_modify_code
  - Use kstop_machine and wait an NMI.
  - Temporarily clear the kernel text read-only flag entirely 
    (can we use text_poke instead?)

Thank you,

-- 
Masami Hiramatsu
e-mail: mhiramat@redhat.com

      reply	other threads:[~2010-02-24 13:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 22:12 [PATCH -tip v10 0/9] kprobes: Kprobes jump optimization support Masami Hiramatsu
2010-02-18 22:12 ` [PATCH -tip v10 1/9] kprobes/x86: Cleanup RELATIVEJUMP_INSTRUCTION to RELATIVEJUMP_OPCODE Masami Hiramatsu
2010-02-18 22:13 ` [PATCH -tip v10 2/9] kprobes: Introduce generic insn_slot framework Masami Hiramatsu
2010-02-18 22:13 ` [PATCH -tip v10 3/9] kprobes: Introduce kprobes jump optimization Masami Hiramatsu
2010-02-18 22:13 ` [PATCH -tip v10 4/9] kprobes: Jump optimization sysctl interface Masami Hiramatsu
2010-02-18 22:13 ` [PATCH -tip v10 5/9] kprobes/x86: Boost probes when reentering Masami Hiramatsu
2010-02-18 22:13 ` [PATCH -tip v10 6/9] kprobes/x86: Cleanup save/restore registers Masami Hiramatsu
2010-02-18 22:13 ` [PATCH -tip v10 7/9] x86: Add text_poke_smp for SMP cross modifying code Masami Hiramatsu
2010-02-18 22:13 ` [PATCH -tip v10 8/9] kprobes/x86: Support kprobes jump optimization on x86 Masami Hiramatsu
2010-02-18 22:13 ` [PATCH -tip v10 9/9] kprobes: Add documents of jump optimization Masami Hiramatsu
2010-02-22 23:14 ` [PATCH -tip v10 0/9] kprobes: Kprobes jump optimization support Masami Hiramatsu
2010-02-23 17:05   ` Frederic Weisbecker
2010-02-23 17:07 ` Steven Rostedt
2010-02-23 22:27   ` Masami Hiramatsu
2010-02-24 13:41     ` Masami Hiramatsu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B852C79.8000702@redhat.com \
    --to=mhiramat@redhat.com \
    --cc=ananth@in.ibm.com \
    --cc=andersk@ksplice.com \
    --cc=andi@firstfloor.org \
    --cc=compudj@krystal.dyndns.org \
    --cc=dle-develop@lists.sourceforge.net \
    --cc=fweisbec@gmail.com \
    --cc=hch@infradead.org \
    --cc=hpa@zytor.com \
    --cc=jbaron@redhat.com \
    --cc=jkenisto@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=srikar@linux.vnet.ibm.com \
    --cc=systemtap@sources.redhat.com \
    --cc=tabbott@ksplice.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox