| 1234567891011121314151617181920212223242526272829303132333435363738394041 |
- choice
- prompt "Choose kernel unwinder"
- default UNWINDER_PROLOGUE if KALLSYMS
- help
- This determines which method will be used for unwinding kernel stack
- traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack,
- lockdep, and more.
- config UNWINDER_GUESS
- bool "Guess unwinder"
- help
- This option enables the "guess" unwinder for unwinding kernel stack
- traces. It scans the stack and reports every kernel text address it
- finds. Some of the addresses it reports may be incorrect.
- While this option often produces false positives, it can still be
- useful in many cases.
- config UNWINDER_PROLOGUE
- bool "Prologue unwinder"
- depends on KALLSYMS
- help
- This option enables the "prologue" unwinder for unwinding kernel stack
- traces. It unwind the stack frame based on prologue code analyze. Symbol
- information is needed, at least the address and length of each function.
- Some of the addresses it reports may be incorrect (but better than the
- Guess unwinder).
- config UNWINDER_ORC
- bool "ORC unwinder"
- depends on HAVE_OBJTOOL
- select OBJTOOL
- help
- This option enables the ORC (Oops Rewind Capability) unwinder for
- unwinding kernel stack traces. It uses a custom data format which is
- a simplified version of the DWARF Call Frame Information standard.
- Enabling this option will increase the kernel's runtime memory usage
- by roughly 2-4MB, depending on your kernel config.
- endchoice
|
