From: Andi Kleen <andi@firstfloor.org>
To: jmerkey@wolfmountaingroup.com
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Jeremy Fitzhardinge" <jeremy@goop.org>,
"Nick Piggin" <nickpiggin@yahoo.com.au>,
"Stefan Richter" <stefanr@s5r6.in-berlin.de>,
paulmck@linux.vnet.ibm.com,
"Peter Zijlstra" <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
"David Howells" <dhowells@redhat.com>
Subject: Re: [ANNOUNCE] mdb: Merkey's Linux Kernel Debugger 2.6.27-rc4 released
Date: Tue, 26 Aug 2008 10:26:57 +0200 [thread overview]
Message-ID: <87prnw9o6m.fsf@basil.nowhere.org> (raw)
In-Reply-To: <51467.166.70.238.43.1219551931.squirrel@webmail.wolfmountaingroup.com> (jmerkey@wolfmountaingroup.com's message of "Sat, 23 Aug 2008 22:25:31 -0600 (MDT)")
jmerkey@wolfmountaingroup.com writes:
> Results from Analysis of GCC volatile/memory barriers
So the result was that barrier()s actually worked? Great.
BTW if you did this work it might be worthwhile to go one further
step: gcc has a test suite where they run small programs and have a
simple facility to scan the resulting assembler code for specific
patterns. If you could bring your examples into that format (as in
being stand alone compiled and have a simple "yes/no" pattern to
check) and let it be included there that might make sure this always
keeps working in the future.
-Andi
next prev parent reply other threads:[~2008-08-26 8:27 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 2:50 [ANNOUNCE] mdb: Merkey's Linux Kernel Debugger 2.6.27-rc4 released jmerkey
2008-08-21 10:07 ` Peter Zijlstra
2008-08-21 10:57 ` Stefan Richter
2008-08-21 11:02 ` Peter Zijlstra
2008-08-21 11:47 ` Paul E. McKenney
2008-08-21 12:03 ` Peter Zijlstra
2008-08-21 14:53 ` Paul E. McKenney
2008-08-21 14:58 ` jmerkey
2008-08-21 12:05 ` Stefan Richter
2008-08-21 12:26 ` jmerkey
[not found] ` <43593.166.70.238.46.1219321595.squirrel@webmail.wolfmountaingroup.com >
2008-08-21 12:35 ` jmerkey
2008-08-21 13:37 ` Nick Piggin
2008-08-21 14:09 ` Stefan Richter
2008-08-22 1:40 ` Nick Piggin
2008-08-22 6:32 ` Stefan Richter
2008-08-22 11:54 ` jmerkey
2008-08-22 12:36 ` Stefan Richter
2008-08-21 14:09 ` Peter Zijlstra
2008-08-21 14:30 ` Paul E. McKenney
2008-08-21 14:14 ` jmerkey
2008-08-21 14:48 ` Peter Zijlstra
2008-08-21 16:21 ` Avi Kivity
2008-08-21 21:06 ` Jeremy Fitzhardinge
2008-08-21 21:18 ` Linus Torvalds
2008-08-21 21:21 ` Jeremy Fitzhardinge
2008-08-24 4:25 ` jmerkey
2008-08-26 8:26 ` Andi Kleen [this message]
2008-08-27 1:49 ` jmerkey
2008-08-22 1:37 ` Nick Piggin
2008-08-21 14:02 ` Stefan Richter
2008-08-21 14:08 ` jmerkey
2008-08-21 15:22 ` Stefan Richter
2008-08-21 15:02 ` jmerkey
2008-08-21 15:57 ` Linus Torvalds
2008-08-21 16:18 ` Linus Torvalds
2008-08-21 16:48 ` Paul E. McKenney
2008-09-24 0:01 ` Paul E. McKenney
2008-08-21 16:43 ` Paul E. McKenney
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=87prnw9o6m.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=dhowells@redhat.com \
--cc=jeremy@goop.org \
--cc=jmerkey@wolfmountaingroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=stefanr@s5r6.in-berlin.de \
--cc=torvalds@linux-foundation.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 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.