diff options
author | Frederic Weisbecker <[email protected]> | 2017-11-06 16:01:23 +0100 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2017-11-08 11:13:50 +0100 |
commit | 7a10e2a9190628a4024ea394ce7bd641ae40ffd1 (patch) | |
tree | e87b2bec06bfc28654d4ba7848b2ed91e65a67bd /tools/perf/util/trace-event-scripting.c | |
parent | 83efcbd028ad3aec36b5a3882cfa32490c135df7 (diff) |
x86: Use lockdep to assert IRQs are disabled/enabled
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.
It also makes no more sense to fix the IRQ flags when a bug is detected
as the assertion is now pure config-dependent debugging. And to quote
Peter Zijlstra:
The whole if !disabled, disable logic is uber paranoid programming,
but I don't think we've ever seen that WARN trigger, and if it does
(and then burns the kernel) we at least know what happend.
Signed-off-by: Frederic Weisbecker <[email protected]>
Acked-by: Thomas Gleixner <[email protected]>
Cc: David S . Miller <[email protected]>
Cc: Lai Jiangshan <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Paul E. McKenney <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Tejun Heo <[email protected]>
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/util/trace-event-scripting.c')
0 files changed, 0 insertions, 0 deletions