diff options
author | Thomas Gleixner <tglx@linutronix.de> | 2021-11-29 20:46:48 +0300 |
---|---|---|
committer | Peter Zijlstra <peterz@infradead.org> | 2021-12-04 12:56:23 +0300 |
commit | 0c1d7a2c2d32fac7ff4a644724b2d52a64184645 (patch) | |
tree | 7d973e81c916d17c106e916ba9c3ec63cbf93865 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | a3642021923b26d86bb27d88c826494827612c06 (diff) | |
download | linux-0c1d7a2c2d32fac7ff4a644724b2d52a64184645.tar.xz |
lockdep: Remove softirq accounting on PREEMPT_RT.
There is not really a softirq context on PREEMPT_RT. Softirqs on
PREEMPT_RT are always invoked within the context of a threaded
interrupt handler or within ksoftirqd. The "in-softirq" context is
preemptible and is protected by a per-CPU lock to ensure mutual
exclusion.
There is no difference on PREEMPT_RT between spin_lock_irq() and
spin_lock() because the former does not disable interrupts. Therefore
if a lock is used in_softirq() and locked once with spin_lock_irq()
then lockdep will report this with "inconsistent {SOFTIRQ-ON-W} ->
{IN-SOFTIRQ-W} usage".
Teach lockdep that we don't really do softirqs on -RT.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lore.kernel.org/r/20211129174654.668506-6-bigeasy@linutronix.de
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions