From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Martin Bligh <mbligh@google.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
prasanna@in.ibm.com, Andrew Morton <akpm@osdl.org>,
Ingo Molnar <mingo@elte.hu>, Paul Mundt <lethal@linux-sh.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jes Sorensen <jes@sgi.com>, Tom Zanussi <zanussi@us.ibm.com>,
Richard J Moore <richardj_moore@uk.ibm.com>,
Michel Dagenais <michel.dagenais@polymtl.ca>,
Christoph Hellwig <hch@infradead.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
William Cohen <wcohen@redhat.com>,
ltt-dev@shafik.org, systemtap@sources.redhat.com,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Karim Yaghmour <karim@opersys.com>, Pavel Machek <pavel@suse.cz>,
Joe Perches <joe@perches.com>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
"Jose R. Santos" <jrs@us.ibm.com>
Subject: Re: [PATCH] Linux Kernel Markers 0.13 for 2.6.17
Date: Tue, 26 Sep 2006 16:05:14 -0400 [thread overview]
Message-ID: <20060926200514.GB12532@Krystal> (raw)
In-Reply-To: <y0mhcyue7ch.fsf@ton.toronto.redhat.com>
* Frank Ch. Eigler (fche@redhat.com) wrote:
> Mathieu Desnoyers <compudj@krystal.dyndns.org> writes:
>
> > [...]
> > > Yep, that looks reasonable. Though you could just directly test a
> > > per-marker enable flag, rather than using "condition"...
> > [...]
> > I am not sure I understand your suggestion correctly.. do you mean having
> > a per-marker flag that would be loaded and tested at every marker site ?
>
> I gather that one reason for working so hard with the inline assembly
> is a race condition problem with the plain STAP_MARK style of marker
> disconnection:
>
> if (pointer) (*pointer)(args ...);
>
> Granted, but this problem could almost certainly be dealt with simpler
> than that. How about a compxchg or other atomic-fetch of the static
> pointer with a local variable? That should solve the worry of an
> (*NULL) call.
>
I don't really see how cmpxchg might be needed here.
Atomic fetch of a static variable is how I will do it in my next version for the
non optimized case :
volatile static var = 0;
if(var) {
preempt disable
call
preempt_enable_no_resched
}
But, still, in the optimized case, the if(var) will depend on an immediate
value, therefore saving the memory read.
> If we then become concerned with a valid pointer become obsolete (the
> probe handler function wanting to unload), we might be able to use
> some RCU-type deferral mechanism and/or preempt controls to ensure
> that this does not happen.
>
This is exactly why the preemption is disabled around the call. However, RCU
must always _see_ a coherent version of the structure in memory.
Calling an empty function, disabling preemption around the call and calling
synchronize_sched() before deleting the removed function looks very much like
a RCU-style protection (actually, that's what it is).
Mathieu
OpenPGP public key: http://krystal.dyndns.org:8080/key/compudj.gpg
Key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2006-09-26 20:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 23:33 [PATCH] Linux Kernel Markers 0.13 for 2.6.17 Mathieu Desnoyers
2006-09-25 23:56 ` Mathieu Desnoyers
2006-09-26 0:16 ` Jeremy Fitzhardinge
2006-09-26 0:25 ` Mathieu Desnoyers
2006-09-26 0:45 ` Mathieu Desnoyers
2006-09-26 1:02 ` Jeremy Fitzhardinge
2006-09-26 2:59 ` Mathieu Desnoyers
2006-09-26 5:03 ` Jeremy Fitzhardinge
2006-09-26 18:04 ` Mathieu Desnoyers
2006-09-26 18:57 ` Jeremy Fitzhardinge
2006-09-26 19:08 ` Mathieu Desnoyers
2006-09-26 19:49 ` Frank Ch. Eigler
2006-09-26 20:05 ` Mathieu Desnoyers [this message]
2006-09-26 0:06 ` Jeremy Fitzhardinge
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=20060926200514.GB12532@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=fche@redhat.com \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=jeremy@goop.org \
--cc=jes@sgi.com \
--cc=joe@perches.com \
--cc=jrs@us.ibm.com \
--cc=karim@opersys.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@shafik.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mbligh@google.com \
--cc=michel.dagenais@polymtl.ca \
--cc=mingo@elte.hu \
--cc=pavel@suse.cz \
--cc=prasanna@in.ibm.com \
--cc=rdunlap@xenotime.net \
--cc=richardj_moore@uk.ibm.com \
--cc=systemtap@sources.redhat.com \
--cc=tglx@linutronix.de \
--cc=wcohen@redhat.com \
--cc=zanussi@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox