All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 0/4] [git pull v2 @num@/@total@] updates for tip
Date: Fri, 20 Feb 2009 14:32:39 -0500	[thread overview]
Message-ID: <20090220193239.561624242@goodmis.org> (raw)


Ingo,

I incorporated your comments, and rebased against your tip/x86/urgent
branch.

Updates are:
 - rename ftrace_arch_modify_* to ftrace_arch_code_modify_*
 - use pr_debug over KERN_INFO in set_kernel_text_*
 - removed comment about ftrace on set_kernel_text_*
 - use return instead of goto to break out of double loop
 - merged akpm's suggestion into 2cd patch

My last commit is:

 4377245aa93b65b6597e4b7bb460fb9abc48b56b
 ftrace: break out modify loop immediately on detection of error

Because I did recently rebase, you might want to confirm that
the SHA1 matches and is not stale data.

Please pull the latest tip/x86/ftrace tree, which can be found at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
tip/x86/ftrace


Steven Rostedt (4):
      ftrace: allow archs to preform pre and post process for code modification
      ftrace, x86: make kernel text writable only for conversions
      ftrace: immediately stop code modification if failure is detected
      ftrace: break out modify loop immediately on detection of error

----
 arch/x86/include/asm/cacheflush.h |    5 +++++
 arch/x86/kernel/ftrace.c          |   17 +++++++++++++++++
 arch/x86/mm/init_32.c             |   35 ++++++++++++++++++++++++++++++++---
 arch/x86/mm/init_64.c             |   37 ++++++++++++++++++++++++++++++++-----
 include/linux/ftrace.h            |    3 +++
 kernel/trace/ftrace.c             |   33 ++++++++++++++++++++++++++++++++-
 6 files changed, 121 insertions(+), 9 deletions(-)

-- 

             reply	other threads:[~2009-02-20 19:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20 19:32 Steven Rostedt [this message]
2009-02-20 19:32 ` [PATCH 1/4] ftrace: allow archs to preform pre and post process for code modification Steven Rostedt
2009-02-20 19:32 ` [PATCH 2/4] ftrace, x86: make kernel text writable only for conversions Steven Rostedt
2009-02-20 19:32 ` [PATCH 3/4] ftrace: immediately stop code modification if failure is detected Steven Rostedt
2009-02-20 19:32 ` [PATCH 4/4] ftrace: break out modify loop immediately on detection of error Steven Rostedt
2009-02-22 17:10 ` [PATCH 0/4] [git pull v2 @num@/@total@] updates for tip Ingo Molnar

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=20090220193239.561624242@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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.