timers/hrtimer: Use lockdep to assert IRQs are disabled/enabled
authorFrederic Weisbecker <frederic@kernel.org>
Mon, 6 Nov 2017 15:01:21 +0000 (16:01 +0100)
committerIngo Molnar <mingo@kernel.org>
Wed, 8 Nov 2017 10:13:49 +0000 (11:13 +0100)
Use lockdep to check that IRQs are enabled or disabled as expected. This
way the sanity check only shows overhead when concurrency correctness
debug code is enabled.

Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Cc: David S . Miller <davem@davemloft.net>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Tejun Heo <tj@kernel.org>
Link: http://lkml.kernel.org/r/1509980490-4285-6-git-send-email-frederic@kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
kernel/time/hrtimer.c

index 88f75f92ef368c53ba8f2a1832068dbe9710cb49..d32520840fde9b1d0e63a4be7d96e092ddd06acf 100644 (file)
@@ -758,9 +758,7 @@ void clock_was_set(void)
  */
 void hrtimers_resume(void)
 {
-       WARN_ONCE(!irqs_disabled(),
-                 KERN_INFO "hrtimers_resume() called with IRQs enabled!");
-
+       lockdep_assert_irqs_disabled();
        /* Retrigger on the local CPU */
        retrigger_next_event(NULL);
        /* And schedule a retrigger for all others */