From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Ingo Molnar <mingo@redhat.com>, linux-kernel@vger.kernel.org
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
Jiri Kosina <jkosina@suse.cz>,
Steven Rostedt <rostedt@goodmis.org>,
Jason Baron <jbaron@akamai.com>,
yrl.pp-manager.tt@hitachi.com, Borislav Petkov <bpetkov@suse.de>
Subject: [PATCH -tip 0/3] kprobes, x86: Move optprobe on top of int3-based instruction patching
Date: Thu, 18 Jul 2013 20:47:38 +0900 [thread overview]
Message-ID: <20130718114738.26675.85914.stgit@mhiramat-M0-7522> (raw)
Hi,
Here is a series of kprobes and x86 patches for moving
optprobe (jump optimized kprobe) onto the int3-based
instruction patching (a.k.a. text_poke_bp, introduced by
Jiri Kosina).
Since this completely moves text_poke_smp* user to new
text_poke_bp, I also remove the old text_poke_smp* code
from alternative.c. As a side effect, it also fixes a
Kconfig warning about CONFIG_STOP_MACHINE dependency
confliction.
Thank you,
---
Masami Hiramatsu (3):
[CLEANUP] kprobes/x86: Remove an incorrect comment about int3 in NMI/MCE
kprobes/x86: Use text_poke_bp() instead of text_poke_smp*()
x86: Remove unused text_poke_smp and text_poke_smp_batch
arch/x86/Kconfig | 5 --
arch/x86/include/asm/alternative.h | 11 ----
arch/x86/kernel/alternative.c | 98 +-------------------------------
arch/x86/kernel/kprobes/common.h | 5 --
arch/x86/kernel/kprobes/core.c | 2 -
arch/x86/kernel/kprobes/opt.c | 110 +++++++-----------------------------
6 files changed, 25 insertions(+), 206 deletions(-)
--
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
IT Management Research Dept. and Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
next reply other threads:[~2013-07-18 11:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 11:47 Masami Hiramatsu [this message]
2013-07-18 11:47 ` [PATCH -tip 1/3] [CLEANUP] kprobes/x86: Remove an incorrect comment about int3 in NMI/MCE Masami Hiramatsu
2013-07-21 13:43 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2013-07-18 11:47 ` [PATCH -tip 2/3] kprobes/x86: Use text_poke_bp() instead of text_poke_smp*() Masami Hiramatsu
2013-07-21 13:43 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2013-07-18 11:47 ` [PATCH -tip 3/3] x86: Remove unused text_poke_smp and text_poke_smp_batch Masami Hiramatsu
2013-07-21 13:43 ` [tip:perf/core] kprobes/x86: Remove unused text_poke_smp() and text_poke_smp_batch() functions tip-bot for Masami Hiramatsu
2013-07-22 7:18 ` [tip:x86/jumplabel] " tip-bot for Masami Hiramatsu
2013-07-22 7:43 ` [PATCH -tip 3/3] x86: Remove unused text_poke_smp and text_poke_smp_batch Ingo Molnar
2013-07-22 8:04 ` Masami Hiramatsu
2013-07-22 8:21 ` Ingo Molnar
2013-07-22 8:38 ` Masami Hiramatsu
2013-07-22 10:01 ` Ingo Molnar
2013-07-22 10:11 ` Masami Hiramatsu
2013-07-22 10:21 ` Ingo Molnar
2013-07-22 13:53 ` Jiri Kosina
2013-07-23 8:10 ` Ingo Molnar
2013-07-18 22:24 ` [PATCH -tip 0/3] kprobes, x86: Move optprobe on top of int3-based instruction patching Jiri Kosina
2013-07-20 1:35 ` Steven Rostedt
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=20130718114738.26675.85914.stgit@mhiramat-M0-7522 \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=bpetkov@suse.de \
--cc=hpa@linux.intel.com \
--cc=jbaron@akamai.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=yrl.pp-manager.tt@hitachi.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;
as well as URLs for NNTP newsgroup(s).