[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45184885.8020807@goop.org>
Date: Mon, 25 Sep 2006 14:22:13 -0700
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Mathieu Desnoyers <compudj@...stal.dyndns.org>
CC: Martin Bligh <mbligh@...gle.com>,
"Frank Ch. Eigler" <fche@...hat.com>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
prasanna@...ibm.com, Andrew Morton <akpm@...l.org>,
Ingo Molnar <mingo@...e.hu>, Paul Mundt <lethal@...ux-sh.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Jes Sorensen <jes@....com>, Tom Zanussi <zanussi@...ibm.com>,
Richard J Moore <richardj_moore@...ibm.com>,
Michel Dagenais <michel.dagenais@...ymtl.ca>,
Christoph Hellwig <hch@...radead.org>,
Greg Kroah-Hartman <gregkh@...e.de>,
Thomas Gleixner <tglx@...utronix.de>,
William Cohen <wcohen@...hat.com>, ltt-dev@...fik.org,
systemtap@...rces.redhat.com, Alan Cox <alan@...rguk.ukuu.org.uk>,
Karim Yaghmour <karim@...rsys.com>,
Pavel Machek <pavel@...e.cz>, Joe Perches <joe@...ches.com>,
"Randy.Dunlap" <rdunlap@...otime.net>,
"Jose R. Santos" <jrs@...ibm.com>
Subject: Re: [PATCH] Linux Kernel Markers 0.11 for 2.6.17
Mathieu Desnoyers wrote:
> Better idea : we could put a read/write dependency on a memory location.
>
Yes, that works well. And it needn't even exist:
extern int __marker_sequencer; /* doesn't exist, never referenced */
asm volatile("first asm" : "+m" (__marker_sequencer));
asm volatile("second asm" : "+m" (__marker_sequencer));
This keeps the asms ordered with respect to each other (and prevents to
independent markers from being intermingled), but it doesn't prevent
them from being re-ordered with respect to other code.
J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists