From: Michael Ellerman <michael@ellerman.id.au>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3][RFC] ftrace/ppc: Have PPC skip updating with stop_machine()
Date: Fri, 08 Jun 2012 14:13:16 +1000 [thread overview]
Message-ID: <1339128796.3330.7.camel@concordia> (raw)
In-Reply-To: <20120426183508.749515835@goodmis.org>
On Thu, 2012-04-26 at 14:31 -0400, Steven Rostedt wrote:
> plain text document attachment
> (0001-ftrace-ppc-Have-PPC-skip-updating-with-stop_machine.patch)
> From: Steven Rostedt <srostedt@redhat.com>
>
> PPC does not have the synchronization issues that x86 has with
> modifying code on one CPU while another CPU is executing it.
> The other CPU will either see the old or new code without any
> issues, unlike x86 which may issue a GPF.
>
> Instead of calling the heavy stop_machine, just update the code.
This looks nice, but it's giving me this:
arch/powerpc/kernel/ftrace.c:497:13: error: static declaration of 'ftrace_replace_code' follows non-static declaration
include/linux/ftrace.h:317:13: note: previous declaration of 'ftrace_replace_code' was here
I think the fix is just to make our ftrace_replace_code() non-static?
cheers
> +static void ftrace_replace_code(int enable)
> +{
> + struct ftrace_rec_iter *iter;
> + struct dyn_ftrace *rec;
> + int ret;
> +
> + for (iter = ftrace_rec_iter_start(); iter;
> + iter = ftrace_rec_iter_next(iter)) {
> + rec = ftrace_rec_iter_record(iter);
> + ret = __ftrace_replace_code(rec, enable);
> + if (ret) {
> + ftrace_bug(ret, rec->ip);
> + return;
> + }
> + }
> +}
> +
next prev parent reply other threads:[~2012-06-08 4:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 18:31 [PATCH 0/3][RFC] powerpc/ftrace: Removal of stop machine (and other goodies) Steven Rostedt
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 [this message]
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=1339128796.3330.7.camel@concordia \
--to=michael@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rostedt@goodmis.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).