From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: [PATCH 0/3][RFC] powerpc/ftrace: Removal of stop machine (and other goodies)
Date: Thu, 26 Apr 2012 14:31:16 -0400 [thread overview]
Message-ID: <20120426183116.857877522@goodmis.org> (raw)
Benjamin,
You once told me on IRC that powerpc has no problem with modifying
code on one CPU that may be executing on another CPU. With the tests I
made on my PPC64 (2 CPUs) box, it seems to be the case.
The first patch removes stop_machine from powerpc. The other patches
add some error handling if ftrace detects an update didn't occur
with 'patch_instruction'.
This is just an RFC, but if it's fine, feel free to pull them into
your tree.
-- Steve
Steven Rostedt (3):
ftrace/ppc: Have PPC skip updating with stop_machine()
powerpc: Have patch_instruction detect faults
ftrace/ppc: Use patch_instruction instead of probe_kernel_write()
----
arch/powerpc/include/asm/code-patching.h | 4 +-
arch/powerpc/kernel/ftrace.c | 69 ++++++++++++++++++++++++------
arch/powerpc/lib/code-patching.c | 14 ++++--
3 files changed, 68 insertions(+), 19 deletions(-)
next reply other threads:[~2012-04-26 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 18:31 Steven Rostedt [this message]
2012-04-26 18:31 ` [PATCH 1/3][RFC] ftrace/ppc: Have PPC skip updating with stop_machine() Steven Rostedt
2012-06-08 4:13 ` Michael Ellerman
2012-04-26 18:31 ` [PATCH 2/3][RFC] powerpc: Have patch_instruction detect faults Steven Rostedt
2012-04-26 18:31 ` [PATCH 3/3][RFC] ftrace/ppc: Use patch_instruction instead of probe_kernel_write() 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=20120426183116.857877522@goodmis.org \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
/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).