From: tixy@yxit.co.uk (Tixy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: kprobes: only patch instructions on one CPU
Date: Thu, 13 Oct 2011 10:07:32 +0100 [thread overview]
Message-ID: <1318496852.2213.39.camel@computer2> (raw)
In-Reply-To: <1318492515.2265.51.camel@computer2>
On Thu, 2011-10-13 at 08:55 +0100, Tixy wrote:
> On Wed, 2011-10-12 at 21:42 +0530, Rabin Vincent wrote:
> > The text patching needs to be done only once, instead of once on
> each
> > CPU. The other CPUs will busy wait inside the stop machine code
> until
> > the patching is done.
>
> Where in the stop machine code do the other CPU's busy wait?
>
> How I read the code is that __stop_cpus() calls queue_stop_cpus_work()
> which queues the work on each of the specified CPU's work list and
> wakes
> that CPU's stopper thread to process it. __stop_cpus() then calls
> wait_for_completion() to wait for these CPUs to finish the work.
>
> I don't see how the execution path of CPUs not specified in cpumask is
> interrupted in any way.
>
As I said in my reply to the other mail, I had missed the fact that it
is stop_machine_cpu_stop() which is used to call our function, and this
synchronises all cores. Therefore, this patch is correct, assuming that
a flush_icache_range executed on one core also flushes I-caches on other
cores. (I'm a bit doubtfull of this as I beleive that at least
ARM11MPCore requires this to be managed in software and I can't find any
code that handles this.)
--
Tixy
>
> >
> > Cc: Jon Medhurst <tixy@yxit.co.uk>
> > Cc: Nicolas Pitre <nicolas.pitre@linaro.org>
> > Signed-off-by: Rabin Vincent <rabin@rab.in>
> > ---
> > arch/arm/kernel/kprobes.c | 4 ++--
> > 1 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/arm/kernel/kprobes.c b/arch/arm/kernel/kprobes.c
> > index 129c116..e9f95300 100644
> > --- a/arch/arm/kernel/kprobes.c
> > +++ b/arch/arm/kernel/kprobes.c
> > @@ -127,7 +127,7 @@ void __kprobes arch_arm_kprobe(struct kprobe *p)
> > flush_insns(addr, sizeof(u16));
> > } else if (addr & 2) {
> > /* A 32-bit instruction spanning two words needs
> special care */
> > - stop_machine(set_t32_breakpoint, (void *)addr,
> &cpu_online_map);
> > + stop_machine(set_t32_breakpoint, (void *)addr, NULL);
> > } else {
> > /* Word aligned 32-bit instruction can be written
> atomically */
> > u32 bkp = KPROBE_THUMB32_BREAKPOINT_INSTRUCTION;
> > @@ -190,7 +190,7 @@ int __kprobes __arch_disarm_kprobe(void *p)
> >
> > void __kprobes arch_disarm_kprobe(struct kprobe *p)
> > {
> > - stop_machine(__arch_disarm_kprobe, p, &cpu_online_map);
> > + stop_machine(__arch_disarm_kprobe, p, NULL);
> > }
> >
> > void __kprobes arch_remove_kprobe(struct kprobe *p)
>
>
>
next prev parent reply other threads:[~2011-10-13 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 16:12 [PATCH] ARM: kprobes: only patch instructions on one CPU Rabin Vincent
2011-10-13 7:55 ` Tixy
2011-10-13 9:07 ` Tixy [this message]
2011-10-25 15:36 ` Rabin Vincent
2011-10-26 6:28 ` Tixy
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=1318496852.2213.39.camel@computer2 \
--to=tixy@yxit.co.uk \
--cc=linux-arm-kernel@lists.infradead.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).