Searched refs:lockdep (Results 1 – 25 of 2424) sorted by relevance
12345678910>>...97
| /linux/Documentation/RCU/ |
| 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 …]
|
| 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.
|
| A D | index.rst | 14 lockdep
15 lockdep-splat
|
| A D | checklist.rst | 70 is less readable and prevents lockdep from detecting locking issues.
152 is common to readers and updaters. However, lockdep
154 of an RCU read-side critical section. See lockdep.txt
320 order to keep lockdep happy, in this case, rcu_dereference_bh().
326 are provided for this case, as discussed in lockdep.txt.
409 use srcu_dereference() in order to avoid lockdep splats.
|
| 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
988 All: lockdep-checked RCU-protected pointer access::
|
| /linux/Documentation/translations/zh_CN/core-api/irq/ |
| A D | irqflags-tracing.rst | 38 irq-flags-track的大部分时间都是在这种状态下度过的：看看lockdep的警告，试着
40 能中没有出现lockdep警告的情况下，arch支持就完成了。
45 一般来说，在一个架构中，不完整的irq-flags-tracing实现是没有风险的：lockdep
|
| /linux/Documentation/translations/zh_CN/process/ |
| A D | 4.Coding.rst | 195 其中一个较重的调试工具是锁检查器或“lockdep”。该工具将跟踪系统中每个锁
198 说，lockdep可以找到许多导致系统死锁的场景。在部署的系统中，这种问题可能会
200 任何类型的非普通锁的代码在提交合并前应在启用lockdep的情况下运行测试。
|
| A D | submit-checklist.rst | 72 15) 所有代码路径都已在启用所有lockdep功能的情况下运行。
|
| /linux/Documentation/translations/zh_TW/process/ |
| A D | 4.Coding.rst | 198 其中一個較重的調試工具是鎖檢查器或「lockdep」。該工具將跟蹤系統中每個鎖
201 說，lockdep可以找到許多導致系統死鎖的場景。在部署的系統中，這種問題可能會
203 任何類型的非普通鎖的代碼在提交合併前應在啓用lockdep的情況下運行測試。
|
| A D | submit-checklist.rst | 75 15) 所有代碼路徑都已在啓用所有lockdep功能的情況下運行。
|
| /linux/Documentation/translations/zh_CN/dev-tools/ |
| A D | testing-overview.rst | 100 * lockdep是一个锁定正确性检测器。参阅
101 Documentation/locking/lockdep-design.rst
|
| /linux/Documentation/core-api/irq/ |
| 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/kernel/entry/ |
| A D | common.c | 447 irq_state.lockdep = lockdep_hardirqs_enabled(); in irqentry_nmi_enter()
466 if (irq_state.lockdep) { in irqentry_nmi_exit()
474 if (irq_state.lockdep) in irqentry_nmi_exit()
|
| /linux/scripts/coccinelle/misc/ |
| 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/kernel/rcu/ |
| 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
|
| /linux/Documentation/locking/ |
| 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
|
| A D | index.rst | 11 lockdep-design
|
| 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:
|
| /linux/Documentation/features/locking/lockdep/ |
| A D | arch-support.txt | 2 # Feature name: lockdep
|
| /linux/kernel/locking/ |
| A D | Makefile | 19 obj-$(CONFIG_LOCKDEP) += lockdep.o
|
| /linux/include/linux/ |
| A D | entry-common.h | 414 bool lockdep; member
|
| /linux/Documentation/translations/ja_JP/ |
| A D | SubmitChecklist | 77 14: lockdepの機能を全て有効にした上で、全てのコードパスを評価してください。
|
| /linux/Documentation/dev-tools/ |
| A D | testing-overview.rst | 105 * lockdep is a locking correctness validator. See
106 Documentation/locking/lockdep-design.rst
|
| /linux/Documentation/translations/zh_CN/core-api/ |
| A D | xarray.rst | 241 意味着你有权使用像__xa_erase()这样的函数而不占用xa_lock；xa_lock是用来进行lockdep验证的，将来也
|
| /linux/Documentation/process/ |
| A D | 4.Coding.rst | 273 One of the heavier debugging tools is the locking checker, or "lockdep."
279 lockdep can find a number of scenarios in which the system could, on rare
281 developers and users) in a deployed system; lockdep allows them to be found
283 locking should be run with lockdep enabled before being submitted for
|
Completed in 41 milliseconds
12345678910>>...97