Thread (305 messages) flat view 305 messages, 27 authors, 2007-09-11

Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures

From: Paul E. McKenney <hidden>
Date: 2007-08-15 23:53:59
Also in: linux-arch, lkml

On Thu, Aug 16, 2007 at 07:41:46AM +0800, Herbert Xu wrote:
On Wed, Aug 15, 2007 at 11:45:20AM -0700, Paul E. McKenney wrote:
quoted
On Wed, Aug 15, 2007 at 07:19:57PM +0100, David Howells wrote:
quoted
Herbert Xu [off-list ref] wrote:
quoted
Let's turn this around.  Can you give a single example where
the volatile semantics is needed in a legitimate way?
Accessing H/W registers?  But apart from that...
Communicating between process context and interrupt/NMI handlers using
per-CPU variables.
Remeber we're talking about atomic_read/atomic_set.  Please
cite the actual file/function name you have in mind.
Yep, we are indeed talking about atomic_read()/atomic_set().

We have been through this issue already in this thread.

							Thanx, Paul
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help