summaryrefslogtreecommitdiff
path: root/Documentation/core-api
diff options
context:
space:
mode:
authorKarl Mehltretter <kmehltretter@gmail.com>2026-09-05 04:37:46 +0200
committerJonathan Corbet <corbet@lwn.net>2026-09-07 10:03:26 -0600
commitb31821013b2331fae246fd6e0530174785b7bca3 (patch)
treef530818b1ea82a23bbe0a07acf55d9c594cc6daf /Documentation/core-api
parentbb2e6adb4739eea65311677316fb40603fd5052c (diff)
downloadlinux-next-b31821013b2331fae246fd6e0530174785b7bca3.tar.gz
linux-next-b31821013b2331fae246fd6e0530174785b7bca3.zip
docs: irqflags-tracing: Fix the lockdep Kconfig option names
CONFIG_PROVE_SPIN_LOCKING, CONFIG_PROVE_RW_LOCKING, CONFIG_PROVE_MUTEX_LOCKING and CONFIG_PROVE_RWSEM_LOCKING have never existed in mainline. Lock proving was merged as the single CONFIG_PROVE_LOCKING, which has depended on CONFIG_TRACE_IRQFLAGS_SUPPORT from the start, so there is no reduced set of options without it. Fixes: 55df314fbdb4 ("[PATCH] lockdep: irqtrace subsystem, docs") Assisted-by: LLM Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net> Message-ID: <20260905023746.82998-1-kmehltretter@gmail.com>
Diffstat (limited to 'Documentation/core-api')
-rw-r--r--Documentation/core-api/irq/irqflags-tracing.rst8
1 files changed, 2 insertions, 6 deletions
diff --git a/Documentation/core-api/irq/irqflags-tracing.rst b/Documentation/core-api/irq/irqflags-tracing.rst
index bdd208259fb3..a3c77046ae6b 100644
--- a/Documentation/core-api/irq/irqflags-tracing.rst
+++ b/Documentation/core-api/irq/irqflags-tracing.rst
@@ -9,12 +9,8 @@ that it gives interested subsystems an opportunity to be notified of
every hardirqs-off/hardirqs-on, softirqs-off/softirqs-on event that
happens in the kernel.
-CONFIG_TRACE_IRQFLAGS_SUPPORT is needed for CONFIG_PROVE_SPIN_LOCKING
-and CONFIG_PROVE_RW_LOCKING to be offered by the generic lock debugging
-code. Otherwise only CONFIG_PROVE_MUTEX_LOCKING and
-CONFIG_PROVE_RWSEM_LOCKING will be offered on an architecture - these
-are locking APIs that are not used in IRQ context. (the one exception
-for rwsems is worked around)
+CONFIG_TRACE_IRQFLAGS_SUPPORT is needed for CONFIG_PROVE_LOCKING to be
+offered by the generic lock debugging code.
Architecture support for this is certainly not in the "trivial"
category, because lots of lowlevel assembly code deal with irq-flags