sched/preempt: Remove PREEMPT_ACTIVE unmasking off in_atomic()
authorFrederic Weisbecker <fweisbec@gmail.com>
Tue, 12 May 2015 14:41:51 +0000 (16:41 +0200)
committerIngo Molnar <mingo@kernel.org>
Tue, 19 May 2015 06:39:13 +0000 (08:39 +0200)
Now that PREEMPT_ACTIVE implies PREEMPT_DISABLE_OFFSET, ignoring
PREEMPT_ACTIVE from in_atomic() check isn't useful anymore.

Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/1431441711-29753-7-git-send-email-fweisbec@gmail.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
include/linux/preempt.h

index 4057696c641c708f8373ba708717e29fa1ea18a7..a1a00e14c14ff1ff506248f57a710f6d01bc426f 100644 (file)
  * used in the general case to determine whether sleeping is possible.
  * Do not use in_atomic() in driver code.
  */
-#define in_atomic()    ((preempt_count() & ~PREEMPT_ACTIVE) != 0)
+#define in_atomic()    (preempt_count() != 0)
 
 /*
  * Check whether we were atomic before we did preempt_disable():