From: Jan Glauber <jan.glauber@de.ibm.com>
To: Mike Grundy <grundym@us.ibm.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-kernel@vger.kernel.org, systemtap@sources.redhat.com
Subject: Re: [PATCH] kprobes for s390 architecture
Date: Thu, 22 Jun 2006 13:28:36 +0200 [thread overview]
Message-ID: <1150975716.6496.9.camel@localhost> (raw)
In-Reply-To: <20060621173436.GA7834@localhost.localdomain>
On Wed, 2006-06-21 at 10:34 -0700, Mike Grundy wrote:
> On Wed, Jun 21, 2006 at 06:38:40PM +0200, Martin Schwidefsky wrote:
> > You misunderstood me here. I'm not talking about storing the same piece
> > of data to memory on each processor. I'm talking about isolating all
> > other cpus so that the initiating cpu can store the breakpoint to memory
> > without running into the danger that another cpu is trying to execute it
> > at the same time. But probably the store should be atomic in regard to
> > instruction fetching on the other cpus. It is only two bytes and it
> > should be aligned.
>
> So maybe something like this:
>
> void smp_replace_instruction(void *info) {
> struct ins_replace_args *parms;
> parms = (struct ins_replace_args *) info;
> *parms->addr = *parms->insn
> }
>
> void __kprobes arch_arm_kprobe(struct kprobe *p)
> {
> struct ins_replace_args parms;
> parms.addr = p->addr;
> parms.insn = BREAKPOINT_INSTRUCTION
>
> preempt_disable();
> smp_call_function(smp_replace_instruction, &parms, 0, 1);
> preempt_enable();
> }
Preemption disabling is not necessary around smp_call_function(), since
smp_call_function() takes a spin lock. But smp_call_function() is wrong
here, it calls the code on all other CPUs but not on our own. Please use
on_each_cpu() instead.
Jan
---
Jan Glauber
IBM Linux Technology Center
Linux on zSeries Development, Boeblingen
next prev parent reply other threads:[~2006-06-22 11:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 13:15 [PATCH] kprobes for s390 architecture Mike Grundy
2006-06-12 19:40 ` Martin Schwidefsky
2006-06-21 4:28 ` Mike Grundy
2006-06-21 16:38 ` Martin Schwidefsky
2006-06-21 17:15 ` Mike Grundy
2006-06-27 11:56 ` Martin Schwidefsky
2006-06-21 17:34 ` Mike Grundy
2006-06-22 11:28 ` Jan Glauber [this message]
2006-06-22 16:36 ` Mike Grundy
2006-06-23 8:50 ` Jan Glauber
2006-06-23 14:38 ` Heiko Carstens
2006-06-22 1:38 ` Mike Grundy
2006-06-21 9:40 ` Jan Glauber
2006-06-21 16:23 ` Jan Glauber
[not found] <20060623150344.GL9446@osiris.boeblingen.de.ibm.com>
2006-06-23 22:53 ` [heiko.carstens@de.ibm.com: Re: [PATCH] kprobes for s390 architecture] Michael Grundy
2006-06-23 22:21 ` [PATCH] kprobes for s390 architecture Heiko Carstens
2006-06-24 11:36 ` Heiko Carstens
2006-06-24 12:15 ` Heiko Carstens
2006-06-25 13:31 ` Mike Grundy
2006-06-26 8:09 ` Heiko Carstens
2006-06-26 10:49 ` Mike Grundy
2006-06-26 11:19 ` Heiko Carstens
2006-06-27 15:23 ` Martin Schwidefsky
2006-06-28 5:58 ` Heiko Carstens
2006-07-07 17:23 ` Mike Grundy
2006-07-07 17:25 ` Heiko Carstens
2006-07-08 18:54 ` Mike Grundy
2006-07-08 19:58 ` Mike Grundy
2006-07-10 9:28 ` Heiko Carstens
2006-07-10 22:20 ` Mike Grundy
2006-07-11 13:54 ` Mike Grundy
2006-07-11 14:13 ` Martin Schwidefsky
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=1150975716.6496.9.camel@localhost \
--to=jan.glauber@de.ibm.com \
--cc=grundym@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=systemtap@sources.redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.