| /OK3568_Linux_fs/kernel/Documentation/RCU/ |
| H A D | lockdep.rst | 4 RCU and lockdep checking
7 All flavors of RCU have lockdep checking available, so that lockdep is
10 that this is not the case in 2.6.32 and earlier). This allows lockdep's
14 In addition, RCU provides the following primitives that check lockdep's
25 positives when lockdep is disabled.
68 expression, but would normally include a lockdep expression. However,
95 This would verify cases #2 and #3 above, and furthermore lockdep would
103 Like rcu_dereference(), when lockdep is enabled, RCU list and hlist
105 critical section. However, a lockdep expression can be passed to them
106 as a additional optional argument. With this lockdep expression, these
[all …]
|
| 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 slat 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 | index.rst | 14 lockdep
15 lockdep-splat
|
| H A D | checklist.rst | 70 is less readable and prevents lockdep from detecting locking issues.
154 is common to readers and updaters. However, lockdep
156 of an RCU read-side critical section. See lockdep.txt
309 order to keep lockdep happy, in this case, rcu_dereference_bh().
315 are provided for this case, as discussed in lockdep.txt.
391 use srcu_dereference() in order to avoid lockdep splats.
|
| H A D | whatisRCU.rst | 312 avoids the lockdep warning that would happen when using (for
317 a lockdep expression to indicate which locks must be acquired
319 a lockdep splat is emitted. See Documentation/RCU/Design/Requirements/Requirements.rst
324 lockdep expression can be added to its list of arguments.
326 the RCU lockdep code would complain only if this instance was
989 All: lockdep-checked RCU-protected pointer access::
|
| /OK3568_Linux_fs/kernel/Documentation/translations/zh_CN/process/ |
| H A D | 4.Coding.rst | 191 其中一个较重的调试工具是锁定检查器或“lockdep”。该工具将跟踪系统中每个锁
194 说，lockdep可以找到许多场景，在这些场景中，系统很少会死锁。在部署的系统中，
196 发现问题。具有任何类型的非普通锁定的代码在提交包含前应在启用lockdep的情况
|
| H A D | submit-checklist.rst | 72 15) 所有代码路径都已在启用所有lockdep功能的情况下运行。
|
| /OK3568_Linux_fs/kernel/tools/lib/lockdep/ |
| H A D | run_tests.sh | 26 timeout 1 ./lockdep "tests/$testname" 2>&1 |
39 …{ timeout 10 valgrind --read-var-info=yes ./lockdep "./tests/$testname" >& "tests/${testname}.vg.o…
|
| H A D | Build | 1 liblockdep-y += common.o lockdep.o preload.o rbtree.o
|
| H A D | Makefile | 66 BIN_FILE = lockdep
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/tools/ |
| H A D | Makefile | 74 $(call descend,lib/lockdep)
118 $(call descend,lib/lockdep,install)
152 $(call descend,lib/lockdep,clean)
|
| /OK3568_Linux_fs/kernel/kernel/entry/ |
| H A D | common.c | 413 irq_state.lockdep = lockdep_hardirqs_enabled(); in irqentry_nmi_enter()
432 if (irq_state.lockdep) { in irqentry_nmi_exit()
440 if (irq_state.lockdep) in irqentry_nmi_exit()
|
| /OK3568_Linux_fs/kernel/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.
|
| /OK3568_Linux_fs/kernel/Documentation/locking/ |
| H A D | seqlock.rst | 98 initialization time, which enables lockdep to validate that the write
101 This lock association is a NOOP if lockdep is disabled and has neither
102 storage nor runtime overhead. If lockdep is enabled, the lock pointer is
103 stored in struct seqcount and lockdep's "lock is held" assertions are
|
| H A D | index.rst | 11 lockdep-design
|
| 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).
|
| /OK3568_Linux_fs/kernel/kernel/rcu/ |
| H A D | Kconfig.debug | 12 bool "RCU list lockdep debugging"
16 Enable RCU lockdep checking for list usages. By default it is
18 need to be converted to pass a lockdep expression. To prevent
|
| /OK3568_Linux_fs/kernel/Documentation/features/locking/lockdep/ |
| H A D | arch-support.txt | 2 # Feature name: lockdep
|
| /OK3568_Linux_fs/kernel/kernel/locking/ |
| H A D | Makefile | 19 obj-$(CONFIG_LOCKDEP) += lockdep.o
|
| /OK3568_Linux_fs/kernel/include/linux/ |
| H A D | entry-common.h | 363 bool lockdep; member
|
| /OK3568_Linux_fs/kernel/Documentation/translations/ja_JP/ |
| H A D | SubmitChecklist | 77 14: lockdepの機能を全て有効にした上で、全てのコードパスを評価してください。
|
| /OK3568_Linux_fs/kernel/Documentation/process/ |
| H A D | 4.Coding.rst | 275 One of the heavier debugging tools is the locking checker, or "lockdep."
281 lockdep can find a number of scenarios in which the system could, on rare
283 developers and users) in a deployed system; lockdep allows them to be found
285 locking should be run with lockdep enabled before being submitted for
|
| H A D | submit-checklist.rst | 78 16) All codepaths have been exercised with all lockdep features enabled.
|