Kconfig.debug (53a2ebaaabc1eb8458796fec3bc1e0e80746b642) Kconfig.debug (ee9f8fce99640811b2b8e79d0d1dbe8bab69ba67)
1menu "Kernel hacking"
2
3config TRACE_IRQFLAGS_SUPPORT
4 def_bool y
5
6source "lib/Kconfig.debug"
7
8config EARLY_PRINTK_USB

--- 291 unchanged lines hidden (view full) ---

300config DEBUG_ENTRY
301 bool "Debug low-level entry code"
302 depends on DEBUG_KERNEL
303 ---help---
304 This option enables sanity checks in x86's low-level entry code.
305 Some of these sanity checks may slow down kernel entries and
306 exits or otherwise impact performance.
307
1menu "Kernel hacking"
2
3config TRACE_IRQFLAGS_SUPPORT
4 def_bool y
5
6source "lib/Kconfig.debug"
7
8config EARLY_PRINTK_USB

--- 291 unchanged lines hidden (view full) ---

300config DEBUG_ENTRY
301 bool "Debug low-level entry code"
302 depends on DEBUG_KERNEL
303 ---help---
304 This option enables sanity checks in x86's low-level entry code.
305 Some of these sanity checks may slow down kernel entries and
306 exits or otherwise impact performance.
307
308 This is currently used to help test NMI code.
309
310 If unsure, say N.
311
312config DEBUG_NMI_SELFTEST
313 bool "NMI Selftest"
314 depends on DEBUG_KERNEL && X86_LOCAL_APIC
315 ---help---
316 Enabling this option turns on a quick NMI selftest to verify
317 that the NMI behaves correctly.

--- 25 unchanged lines hidden (view full) ---

343 checks and (boot time) debug printouts added to the kernel.
344 This debugging adds some small amount of runtime overhead
345 to the kernel.
346
347 If unsure, say N.
348
349config PUNIT_ATOM_DEBUG
350 tristate "ATOM Punit debug driver"
308 If unsure, say N.
309
310config DEBUG_NMI_SELFTEST
311 bool "NMI Selftest"
312 depends on DEBUG_KERNEL && X86_LOCAL_APIC
313 ---help---
314 Enabling this option turns on a quick NMI selftest to verify
315 that the NMI behaves correctly.

--- 25 unchanged lines hidden (view full) ---

341 checks and (boot time) debug printouts added to the kernel.
342 This debugging adds some small amount of runtime overhead
343 to the kernel.
344
345 If unsure, say N.
346
347config PUNIT_ATOM_DEBUG
348 tristate "ATOM Punit debug driver"
351 depends on PCI
352 select DEBUG_FS
353 select IOSF_MBI
354 ---help---
355 This is a debug driver, which gets the power states
356 of all Punit North Complex devices. The power states of
357 each device is exposed as part of the debugfs interface.
358 The current power state can be read from
359 /sys/kernel/debug/punit_atom/dev_power_state
360
349 select DEBUG_FS
350 select IOSF_MBI
351 ---help---
352 This is a debug driver, which gets the power states
353 of all Punit North Complex devices. The power states of
354 each device is exposed as part of the debugfs interface.
355 The current power state can be read from
356 /sys/kernel/debug/punit_atom/dev_power_state
357
358config ORC_UNWINDER
359 bool "ORC unwinder"
360 depends on X86_64
361 select STACK_VALIDATION
362 ---help---
363 This option enables the ORC (Oops Rewind Capability) unwinder for
364 unwinding kernel stack traces. It uses a custom data format which is
365 a simplified version of the DWARF Call Frame Information standard.
366
367 This unwinder is more accurate across interrupt entry frames than the
368 frame pointer unwinder. It can also enable a 5-10% performance
369 improvement across the entire kernel if CONFIG_FRAME_POINTER is
370 disabled.
371
372 Enabling this option will increase the kernel's runtime memory usage
373 by roughly 2-4MB, depending on your kernel config.
374
375config FRAME_POINTER_UNWINDER
376 def_bool y
377 depends on !ORC_UNWINDER && FRAME_POINTER
378
379config GUESS_UNWINDER
380 def_bool y
381 depends on !ORC_UNWINDER && !FRAME_POINTER
382
361endmenu
383endmenu