| /linux/Documentation/translations/zh_CN/core-api/irq/ |
| H A D | irqflags-tracing.rst | 38 irq-flags-track的大部分时间都是在这种状态下度过的：看看lockdep的警告，试着
40 能中没有出现lockdep警告的情况下，arch支持就完成了。
45 一般来说，在一个架构中，不完整的irq-flags-tracing实现是没有风险的：lockdep
|
| /linux/Documentation/RCU/ |
| H A D | lockdep-splat.rst | 11 When such misuse is detected, an lockdep-RCU splat is emitted.
13 The usual cause of a lockdep-RCU splat is someone accessing an
20 So let's look at an example RCU lockdep splat from 3.0-rc5, one that
83 With this change, there would be no lockdep-RCU splat emitted if this
86 the above lockdep-RCU splat because ->queue_lock is held (see #2 in the
105 above lockdep-RCU splat.
115 this change would also suppress the above lockdep-RCU splat.
|
| H A D | checklist.rst | 71 prevents lockdep from detecting locking issues. Acquiring a
168 is common to readers and updaters. However, lockdep
170 of an RCU read-side critical section. See lockdep.rst
353 order to keep lockdep happy, in this case, rcu_dereference_bh().
359 are provided for this case, as discussed in lockdep.rst.
466 use srcu_dereference() in order to avoid lockdep splats.
|
| H A D | whatisRCU.rst | 348 avoids the lockdep warning that would happen when using (for
353 a lockdep expression to indicate which locks must be acquired
355 a lockdep splat is emitted. See Design/Requirements/Requirements.rst
360 lockdep expression can be added to its list of arguments.
362 the RCU lockdep code would complain only if this instance was
1237 All: lockdep-checked RCU utility APIs::
|
| /linux/Documentation/core-api/irq/ |
| H A D | irqflags-tracing.rst | 37 irq-flags-tracing is spent in this state: look at the lockdep
40 lockdep complaint in the irq-flags-tracing functions arch support is
47 implementation in an architecture: lockdep will detect that and will
|
| /linux/Documentation/translations/zh_TW/dev-tools/ |
| H A D | testing-overview.rst | 100 * lockdep是一個鎖定正確性檢測器。參閱
101 Documentation/locking/lockdep-design.rst
|
| /linux/Documentation/translations/zh_CN/scheduler/ |
| H A D | completion.rst | 108 DECLARE_COMPLETION_ONSTACK()来初始化，这不仅仅是为了让lockdep正确运行，也是明确表
126 在堆栈上单纯地调用DECLARE_COMPLETION()会触发一个lockdep警告。
|
| /linux/scripts/coccinelle/misc/ |
| H A D | cond_no_effect.cocci | 6 // information is used (as with lockdep) or where the identity
31 // * look that way and give @of->mutex different static lockdep keys.
|
| /linux/Documentation/translations/it_IT/locking/ |
| H A D | index.rst | 11 lockdep-design
|
| H A D | locktypes.rst | 187 - Se viene abilitato lockdep, allora local_lock ottiene un lockmap che
382 i chiamanti di func3(). L'*assert* di lockdep verrà attivato su un kernel
546 Se queste regole verranno violate, allora lockdep se ne accorgerà e questo sia
|
| H A D | lockstat.rst | 26 (vedere Documentation/translations/it_IT/locking/lockdep-design.rst).
|
| H A D | lockdep-design.rst | 23 vista di lockdep, i due blocchi (L1 ed L2) non sono per forza correlati: quella
391 grep "BD" /proc/lockdep
533 Questo significa che lockdep ha visto acquisire L1 prima di L2 nello stesso
544 grafo delle dipendenze di lockdep:
|
| /linux/Documentation/features/locking/lockdep/ |
| H A D | arch-support.txt | 2 # Feature name: lockdep
|
| /linux/Documentation/translations/zh_CN/locking/ |
| H A D | index.rst | 23 * lockdep-design
|
| /linux/Documentation/process/debugging/ |
| H A D | driver_development_debugging_guide.rst | 162 KASAN, UBSAN, lockdep and other error checkers
187 lockdep (Lock Dependency Validator)
192 lockdep is a runtime lock dependency validator that detects potential deadlocks
196 lockdep is especially useful for validating the correctness of lock ordering in
|
| /linux/tools/testing/selftests/rcutorture/bin/ |
| H A D | torture.sh | 105 echo " --do-srcu-lockdep / --do-no-srcu-lockdep / --no-srcu-lockdep"
212 --do-srcu-lockdep|--do-no-srcu-lockdep|--no-srcu-lockdep)
213 do_srcu_lockdep=`doyesno "$1" --do-srcu-lockdep`
572 echo " --- do-srcu-lockdep:" Start `date` | tee -a $T/log
573 tools/testing/selftests/rcutorture/bin/srcu_lockdep.sh --datestamp "$ds/results-srcu-lockdep" > $T/srcu_lockdep.sh.out 2>&1
575 cp $T/srcu_lockdep.sh.out "tools/testing/selftests/rcutorture/res/$ds/results-srcu-lockdep/lo
[all...] |
| /linux/arch/loongarch/ |
| H A D | Kconfig.debug | 7 lockdep, and more.
|
| /linux/arch/arm64/kernel/ |
| H A D | entry-common.c | 124 state.lockdep = lockdep_hardirqs_enabled(); in arm64_enter_el1_dbg()
142 if (state.lockdep) { in arm64_exit_el1_dbg()
148 if (state.lockdep) in arm64_exit_el1_dbg()
|
| /linux/include/linux/ |
| H A D | irq-entry-common.h | 339 bool lockdep; member
|
| /linux/Documentation/translations/zh_CN/core-api/ |
| H A D | xarray.rst | 242 意味着你有权使用像__xa_erase()这样的函数而不占用xa_lock；xa_lock是用来进行lockdep验证的，将来也
|
| /linux/Documentation/dev-tools/ |
| H A D | testing-overview.rst | 105 * lockdep is a locking correctness validator. See
106 Documentation/locking/lockdep-design.rst
|
| /linux/Documentation/locking/ |
| H A D | lockdep-design.rst | 23 a task is attempting to acquire L2 while holding L1. From lockdep's
340 Exceeding this number will trigger the following lockdep warning::
392 grep "BD" /proc/lockdep
523 , which means lockdep has seen L1 held before L2 held in the same context at runtime.
532 in the lockdep graph:
|
| H A D | lockstat.rst | 20 lock classes. We build on that (see Documentation/locking/lockdep-design.rst).
|
| /linux/Documentation/scheduler/ |
| H A D | completion.rst | 115 explicitly, not just to make lockdep happy, but also to make it clear
139 A naive DECLARE_COMPLETION() on the stack triggers a lockdep warning.
|
| /linux/tools/memory-model/Documentation/ |
| H A D | simple.txt | 49 The Linux kernel's lockdep (CONFIG_PROVE_LOCKING=y) is very helpful with
54 properly with lockdep. For another thing, these primitives have been
|