| Kconfig.debug (06ec64b84c357693e9a5540de8eedfc775dbae12) | Kconfig.debug (87a4c375995ed8eaa721b08825cf73d0b02b3145) |
|---|---|
| 1menu "Kernel hacking" 2 3menu "printk and dmesg options" 4 5config PRINTK_TIME 6 bool "Show timing information on printks" 7 depends on PRINTK 8 help --- 1181 unchanged lines hidden (view full) --- 1190 If you say Y here, the lock dependency engine will do 1191 additional runtime checks to debug itself, at the price 1192 of more runtime overhead. 1193 1194config DEBUG_ATOMIC_SLEEP 1195 bool "Sleep inside atomic section checking" 1196 select PREEMPT_COUNT 1197 depends on DEBUG_KERNEL | 1menu "Kernel hacking" 2 3menu "printk and dmesg options" 4 5config PRINTK_TIME 6 bool "Show timing information on printks" 7 depends on PRINTK 8 help --- 1181 unchanged lines hidden (view full) --- 1190 If you say Y here, the lock dependency engine will do 1191 additional runtime checks to debug itself, at the price 1192 of more runtime overhead. 1193 1194config DEBUG_ATOMIC_SLEEP 1195 bool "Sleep inside atomic section checking" 1196 select PREEMPT_COUNT 1197 depends on DEBUG_KERNEL |
| 1198 depends on !ARCH_NO_PREEMPT |
|
| 1198 help 1199 If you say Y here, various routines which may sleep will become very 1200 noisy if they are called inside atomic sections: when a spinlock is 1201 held, inside an rcu read side critical section, inside preempt disabled 1202 sections, inside an interrupt, etc... 1203 1204config DEBUG_LOCKING_API_SELFTESTS 1205 bool "Locking API boot-time self-tests" --- 837 unchanged lines hidden --- | 1199 help 1200 If you say Y here, various routines which may sleep will become very 1201 noisy if they are called inside atomic sections: when a spinlock is 1202 held, inside an rcu read side critical section, inside preempt disabled 1203 sections, inside an interrupt, etc... 1204 1205config DEBUG_LOCKING_API_SELFTESTS 1206 bool "Locking API boot-time self-tests" --- 837 unchanged lines hidden --- |