Re: [PATCH v2 0/2] tracing: Introduce relative stacktrace

[PATCH v2 0/2] tracing: Introduce relative stacktrace · "Masami Hiramatsu (Google)" <mhiramat@kernel.org> · 2025-02-01
[PATCH v2 1/2] modules: Add __module_build_id() to find module by build_id · "Masami Hiramatsu (Google)" <mhiramat@kernel.org> · 2025-02-01
[PATCH v2 2/2] tracing: Add relative-stacktrace option · "Masami Hiramatsu (Google)" <mhiramat@kernel.org> · 2025-02-01
Re: [PATCH v2 0/2] tracing: Introduce relative stacktrace · Steven Rostedt <rostedt@goodmis.org> · 2025-02-03
Re: [PATCH v2 0/2] tracing: Introduce relative stacktrace · Masami Hiramatsu (Google) <mhiramat@kernel.org> · 2025-02-05
Re: [PATCH v2 0/2] tracing: Introduce relative stacktrace · Masami Hiramatsu (Google) <mhiramat@kernel.org> · 2025-02-05
Re: [PATCH v2 0/2] tracing: Introduce relative stacktrace · Steven Rostedt <rostedt@goodmis.org> · 2025-02-05
Re: [PATCH v2 0/2] tracing: Introduce relative stacktrace · Steven Rostedt <rostedt@goodmis.org> · 2025-02-05
Re: [PATCH v2 0/2] tracing: Introduce relative stacktrace · Masami Hiramatsu (Google) <mhiramat@kernel.org> · 2025-02-06

From: Steven Rostedt <rostedt@goodmis.org>
Date: 2025-02-05 14:52:44
Also in: linux-modules, lkml

On Wed, 5 Feb 2025 21:25:43 +0900
Masami Hiramatsu (Google) [off-list ref] wrote:

Anyway, let me try storing the module table.

I have the module table code almost done. At least the recording of the
modules into persistent memory. Exposing and using it is not started yet. I
can send what I have and you can take it over if you want.

-- Steve

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help