On Thu, 30 Mar 2006, Chen, Kenneth W wrote:
> > static __inline__ void
> > clear_bit (int nr, volatile void *addr)
> > {
> > - __u32 mask, old, new;
> > - volatile __u32 *m;
> > - CMPXCHG_BUGCHECK_DECL
> > -
> > - m = (volatile __u32 *) addr + (nr >> 5);
> > - mask = ~(1 << (nr & 31));
> > - do {
> > - CMPXCHG_BUGCHECK(m);
> > - old = *m;
> > - new = old & mask;
> > - } while (cmpxchg_acq(m, old, new) != old);
> > + clear_bit_mode(nr, addr, MODE_ATOMIC);
> > }
>
> I would make that MODE_RELEASE for clear_bit, simply to match the
> observation that clear_bit is usually used in unlock path and have
> potential less surprises.
clear_bit per se is defined as an atomic operation with no implications
for release or acquire. If it is used for release then either add the
appropriate barrier or use MODE_RELEASE explicitly.
It precise the uncleanness in ia64 that such semantics are attached to
these bit operations which may lead people to depend on those. We need to
either make these explicit or not depend on them.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
