From: David Howells Date: Mon, 16 Oct 2006 13:10:49 +0000 (+0100) Subject: [PATCH] FRV: Use the correct preemption primitives in kmap_atomic() and co X-Git-Tag: v2.6.19-rc3~207 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=29da7eb0ec69245c6e9b4eb5bdaa04af685f5c4f;p=pandora-kernel.git [PATCH] FRV: Use the correct preemption primitives in kmap_atomic() and co Use inc/dec_preempt_count() rather than preempt_enable/disable() and manually add in the compiler barriers that were provided by the latter. This makes FRV consistent with other archs. Furthermore, the compiler barrier effects are now there unconditionally - at least as far as preemption is concerned - because we don't want the compiler moving memory accesses out of the section of code in which the mapping is in force - in effect the kmap_atomic() must imply a LOCK-class barrier and the kunmap_atomic() must imply an UNLOCK-class barrier to the compiler. Signed-off-by: David Howells Acked-by: Peter Zijlstra Signed-off-by: Linus Torvalds --- Reading git-diff-tree failed