[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090220193239.561624242@goodmis.org>
Date: Fri, 20 Feb 2009 14:32:39 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: linux-kernel@...r.kernel.org
Cc: Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Frederic Weisbecker <fweisbec@...il.com>
Subject: [PATCH 0/4] [git pull v2 @num@/@...al@] updates for tip
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(-)
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists