From: Andi Kleen <ak@suse.de>
To: Richard Henderson <rth@redhat.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Chuck Ebbert <76306.1226@compuserve.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [patch] i386: make bitops safe
Date: Tue, 28 Feb 2006 02:24:13 +0100 [thread overview]
Message-ID: <200602280224.13632.ak@suse.de> (raw)
In-Reply-To: <20060228005436.GA24895@redhat.com>
On Tuesday 28 February 2006 01:54, Richard Henderson wrote:
> I think the best argument for simply leaving things with a memory
> clobber is that these are atomic operations, and are on occasion
> used as locks, or parts of locks.
How about __set_bit? It is supposed to be not atomic. What would
be best there?
-Andi
next prev parent reply other threads:[~2006-02-28 1:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 21:57 [patch] i386: make bitops safe Chuck Ebbert
2006-02-27 23:06 ` Linus Torvalds
2006-02-27 23:47 ` Andi Kleen
2006-02-28 0:54 ` Richard Henderson
2006-02-28 1:24 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-28 6:04 Chuck Ebbert
2006-02-28 21:25 ` Richard Henderson
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=200602280224.13632.ak@suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rth@redhat.com \
--cc=torvalds@osdl.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