[lkml]   [1999]   [Sep]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: set_current_state
On Sun, 5 Sep 1999, Jamie Lokier wrote:

>AFAIK the ordering of volatile operations is only defined with respect
>to each other.

I thought the rule was different. If that is true we should add a
barrier() after setting current->state in the UP code. Are you 100% sure
that the compiler can move not-volatile data read/write across the write
of a volatile var?

I can't find this information into the gcc info docs.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:53    [from the cache]
©2003-2014 Jasper Spaans. hosted at Digital Ocean