Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
From: Arjan van de Ven <hidden>
Date: 2007-09-09 18:21:44
Also in:
linux-arch, lkml
From: Arjan van de Ven <hidden>
Date: 2007-09-09 18:21:44
Also in:
linux-arch, lkml
On Sun, 9 Sep 2007 19:02:54 +0100 Denys Vlasenko [off-list ref] wrote:
Why is all this fixation on "volatile"? I don't think people want "volatile" keyword per se, they want atomic_read(&x) to _always_ compile into an memory-accessing instruction, not register access.
and ... why is that? is there any valid, non-buggy code sequence that makes that a reasonable requirement?