From: Will Deacon <will.deacon@arm.com>
To: "Jon Medhurst (Tixy)" <tixy@linaro.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Frederic Weisbecker <fweisbec@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rabin Vincent <rabin@rab.in>, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: ftrace: Ensure code modifications are synchronised across all cpus
Date: Mon, 10 Dec 2012 11:24:08 +0000 [thread overview]
Message-ID: <20121210112408.GC6988@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1355137445.3386.7.camel@linaro1.home>
On Mon, Dec 10, 2012 at 11:04:05AM +0000, Jon Medhurst (Tixy) wrote:
> On Fri, 2012-12-07 at 19:02 +0000, Will Deacon wrote:
> > For ARMv7, there are small subsets of instructions for ARM and Thumb which
> > are guaranteed to be atomic wrt concurrent modification and execution of
> > the instruction stream between different processors:
> >
> > Thumb: The 16-bit encodings of the B, NOP, BKPT, and SVC instructions.
> > ARM: The B, BL, NOP, BKPT, SVC, HVC, and SMC instructions.
> >
>
> So this means for things like kprobes which can modify arbitrary kernel
> code we are going to need to continue to always use some form of
> stop_the_whole_system() function?
>
> Also, kprobes currently uses patch_text() which only uses stop_machine
> for Thumb2 instructions which straddle a word boundary, so this needs
> changing?
Yes; if you're modifying instructions other than those mentioned above, then
you'll need to synchronise the CPUs, update the instructions, perform
cache-maintenance on the writing CPU and then execute an isb on the
executing core (this last bit isn't needed if you're going to go through an
exception return to get back to the new code -- depends on how your
stop/resume code works).
For ftrace we can (hopefully) avoid a lot of this when we have known points
of modification.
Will
next prev parent reply other threads:[~2012-12-10 11:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 18:11 [PATCH] ARM: ftrace: Ensure code modifications are synchronised across all cpus Jon Medhurst (Tixy)
2012-12-06 19:19 ` Steven Rostedt
2012-12-07 9:22 ` Jon Medhurst (Tixy)
2012-12-07 14:03 ` Steven Rostedt
2012-12-07 14:55 ` Jon Medhurst (Tixy)
2012-12-07 15:28 ` Steven Rostedt
2012-12-07 15:40 ` Jon Medhurst (Tixy)
2012-12-07 16:09 ` Steven Rostedt
2012-12-07 16:23 ` Russell King - ARM Linux
2012-12-07 16:36 ` Steven Rostedt
2012-12-07 16:45 ` Russell King - ARM Linux
2012-12-07 17:13 ` Steven Rostedt
2012-12-07 17:45 ` Jon Medhurst (Tixy)
2012-12-07 18:06 ` Steven Rostedt
2012-12-07 18:17 ` Steven Rostedt
2012-12-07 18:18 ` Jon Medhurst (Tixy)
2012-12-10 10:04 ` Will Deacon
2012-12-10 13:02 ` Steven Rostedt
2012-12-10 13:33 ` Will Deacon
2012-12-10 13:40 ` Jamie Lokier
2012-12-10 14:56 ` Will Deacon
2012-12-10 13:57 ` Russell King - ARM Linux
2012-12-10 14:06 ` Steven Rostedt
2012-12-10 14:07 ` Russell King - ARM Linux
2012-12-10 14:46 ` Steven Rostedt
2012-12-10 15:25 ` Russell King - ARM Linux
2012-12-10 16:31 ` Steven Rostedt
2012-12-10 16:45 ` Jon Medhurst (Tixy)
2012-12-07 18:13 ` Russell King - ARM Linux
2012-12-07 18:43 ` Steven Rostedt
2012-12-07 19:02 ` Will Deacon
2012-12-07 20:01 ` Steven Rostedt
2012-12-10 11:04 ` Jon Medhurst (Tixy)
2012-12-10 11:24 ` Will Deacon [this message]
2012-12-10 14:02 ` 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=20121210112408.GC6988@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=fweisbec@gmail.com \
--cc=hpa@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@redhat.com \
--cc=rabin@rab.in \
--cc=rostedt@goodmis.org \
--cc=tixy@linaro.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).