You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add "relative-stacktrace" option to save the stacktrace entries
as offset from the _stext or module's text section. For the
module address, each entry also saves the first 4bytes of the
build_id of the module so that it can find the appropriate
symbol from the offset.
By using this build_id, we can also easily find the corresponding
modules off-line. Thus this stacktrace data is in the persistent
ring buffer, the kernel can find appropriate modules after reboot
without saving previous live information.
This feature also shows the module name after the symbol as below.
event-sample-1622 [005] ...1. 2112.978105: <stack trace>
=> event_triggers_post_call
=> trace_event_raw_event_foo_bar [trace_events_sample]
=> do_simple_thread_func [trace_events_sample]
=> simple_thread [trace_events_sample]
=> kthread
=> ret_from_fork
=> ret_from_fork_asm
The downside is the cost of time and memory (on 32bit arch). This
needs to find the module if the address in the module, and save
both of 32bit offset and 32bit hash for each entry, this may consume
twice memory on 32bit arch. On 64bit arch, the amount of consuming
memory is the same.
Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
0 commit comments