aboutsummaryrefslogtreecommitdiff
path: root/block
diff options
context:
space:
mode:
authorGravatar Jeff Dike <jdike@addtoit.com> 2008-02-04 22:31:09 -0800
committerGravatar Linus Torvalds <torvalds@woody.linux-foundation.org> 2008-02-05 09:44:29 -0800
commitfce8c41c9f68b9af36f3076bae8f1d469a6e7aab (patch)
tree3580fd114bcef42a898c838f5a58ddcb2d29ae99 /block
parentuml: install panic notifier earlier (diff)
downloadlinux-fce8c41c9f68b9af36f3076bae8f1d469a6e7aab.tar.gz
linux-fce8c41c9f68b9af36f3076bae8f1d469a6e7aab.tar.bz2
linux-fce8c41c9f68b9af36f3076bae8f1d469a6e7aab.zip
uml: use barrier() instead of mb()
signals_enabled and pending have requirements on the order in which they are modified. This used to be done by declaring them volatile and putting an mb() where the ordering requirements were in effect. After getting a better (I hope) understanding of how to do this correctly, the volatile declarations are gone and the mb()'s replaced by barrier()'s. One of the mb()'s was deleted because I see no problematic writes that could be re-ordered past that point. Signed-off-by: Jeff Dike <jdike@linux.intel.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions