From: Frederic Weisbecker <fweisbec@gmail.com>
To: Masami Hiramatsu <mhiramat@redhat.com>, Ingo Molnar <mingo@elte.hu>
Cc: 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>,
Steven Rostedt <rostedt@goodmis.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: Tue, 23 Feb 2010 18:05:20 +0100 [thread overview]
Message-ID: <20100223170508.GB5357@nowhere> (raw)
In-Reply-To: <4B830FDB.7010202@redhat.com>
On Mon, Feb 22, 2010 at 06:14:35PM -0500, Masami Hiramatsu wrote:
> Masami Hiramatsu wrote:
> > Hi Ingo,
> >
> > Here are the patchset of the kprobes jump optimization v10
> > (a.k.a. Djprobe). This version just updated a document,
> > and applicable for 2.6.33-rc8-tip.
>
> BTW, this optimization is automatically done in kprobes.
> (no other tools/changes are required for it)
> This means all users including perf-probe have a benefit
> from this feature just by configuring CONFIG_OPTPROBES=y :)
> So it's a part of perf-probe/kprobe-tracer enhancement, IMHO.
>
> Thank you,
Yep. I guess we can give it a try for 2.6.34.
Ingo?
next prev parent reply other threads:[~2010-02-23 17:05 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 [this message]
2010-02-23 17:07 ` Steven Rostedt
2010-02-23 22:27 ` Masami Hiramatsu
2010-02-24 13:41 ` Masami Hiramatsu
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=20100223170508.GB5357@nowhere \
--to=fweisbec@gmail.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=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=jbaron@redhat.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.