linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@redhat.com>
To: Ingo Molnar <mingo@elte.hu>, lkml <linux-kernel@vger.kernel.org>
Cc: "Steven Rostedt" <rostedt@goodmis.org>,
	PrzemysławPawełczyk <przemyslaw@pawelczyk.it>,
	"Frederic Weisbecker" <fweisbec@gmail.com>,
	"Ananth N Mavinakayanahalli" <ananth@in.ibm.com>,
	"Jim Keniston" <jkenisto@us.ibm.com>,
	"Mathieu Desnoyers" <compudj@krystal.dyndns.org>,
	"Jason Baron" <jbaron@redhat.com>,
	systemtap <systemtap@sources.redhat.com>,
	DLE <dle-develop@lists.sourceforge.net>
Subject: [PATCH -tip 0/4] kprobes updates
Date: Tue, 02 Feb 2010 16:48:56 -0500	[thread overview]
Message-ID: <20100202214856.4694.72709.stgit@dhcp-100-2-132.bos.redhat.com> (raw)

Hi,

Here are patches for updating kprobes. Actually, the first patch is
same as that previously I sent to LKML. 2nd-4th patches introduces text
reserve functions for avoiding conflictions between alternatives/
ftrace and kprobes. Since alternatives and ftrace can modify fixed
small pieces of kernel text, I think those should come before kprobes.

Thank you,

---

Masami Hiramatsu (4):
      ftrace: Remove record freezing
      kprobes: Check probe address is reserved
      ftrace/alternatives: Introducing *_text_reserved functions
      [RESEND] kprobes: Disable booster when CONFIG_PREEMPT=y


 arch/ia64/kernel/kprobes.c         |    2 +
 arch/x86/include/asm/alternative.h |    5 +++
 arch/x86/kernel/alternative.c      |   16 +++++++++++
 arch/x86/kernel/kprobes.c          |    5 +++
 include/linux/ftrace.h             |    7 ++++-
 kernel/kprobes.c                   |   33 +++-------------------
 kernel/trace/ftrace.c              |   54 ++++++++++--------------------------
 7 files changed, 52 insertions(+), 70 deletions(-)

-- 
Masami Hiramatsu

Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com

             reply	other threads:[~2010-02-02 21:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02 21:48 Masami Hiramatsu [this message]
2010-02-02 21:49 ` [PATCH -tip 1/4] [RESEND] kprobes: Disable booster when CONFIG_PREEMPT=y Masami Hiramatsu
2010-02-04  9:55   ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-02-02 21:49 ` [PATCH -tip 2/4] ftrace/alternatives: Introducing *_text_reserved functions Masami Hiramatsu
2010-02-04  9:55   ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-02-02 21:49 ` [PATCH -tip 3/4] kprobes: Check probe address is reserved Masami Hiramatsu
2010-02-04  9:55   ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-02-02 21:49 ` [PATCH -tip 4/4] ftrace: Remove record freezing Masami Hiramatsu
2010-02-04  9:55   ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-02-04 13:49   ` [PATCH -tip 4/4] " Steven Rostedt
2010-02-04  9:06 ` [PATCH -tip 0/4] kprobes updates Ingo Molnar
2010-02-04 20:37   ` 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=20100202214856.4694.72709.stgit@dhcp-100-2-132.bos.redhat.com \
    --to=mhiramat@redhat.com \
    --cc=ananth@in.ibm.com \
    --cc=compudj@krystal.dyndns.org \
    --cc=dle-develop@lists.sourceforge.net \
    --cc=fweisbec@gmail.com \
    --cc=jbaron@redhat.com \
    --cc=jkenisto@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=przemyslaw@pawelczyk.it \
    --cc=rostedt@goodmis.org \
    --cc=systemtap@sources.redhat.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).