mirror of
https://github.com/torvalds/linux.git
synced 2024-12-21 02:21:36 +00:00
49aef111e2
It unwind the stack frame based on prologue code analyze. CONFIG_KALLSYMS is needed, at least the address and length of each function. Three stages when we do unwind, 1) unwind_start(), the prapare of unwinding, fill unwind_state. 2) unwind_done(), judge whether the unwind process is finished or not. 3) unwind_next_frame(), unwind the next frame. Dividing unwinder helps to add new unwinders in the future, e.g.: unwinder_frame, unwinder_orc, .etc. Signed-off-by: Qing Zhang <zhangqing@loongson.cn> Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
30 lines
1014 B
Plaintext
30 lines
1014 B
Plaintext
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).
|
|
|
|
endchoice
|