On Sun, Feb 8, 2026 at 11:27 PM Steven Rostedt <[email protected]> wrote: > > On Sun, 8 Feb 2026 21:07:37 +0800 > Donglin Peng <[email protected]> wrote: > > Hi Steve, > > > > I noticed that trace-cmd 3.4 introduced a new feature: > > > > - Add support for showing parent functions in function graph > > > > If the "funcgraph-retaddr" option is set during function graph tracing, > > the parent functions will now be displayed: > > > > preempt_count_add(val=65536); /* <-irq_enter_rcu */ (ret=0x10001) > > > > However, it currently only prints the caller's entry point. I suggest > > enhancing this to include the **offset within the caller** as well. This > > would allow tools like `faddr2line` to locate the exact call site > > accurately. > > Yeah, it makes sense to always show the offset of where it was called. > We can add that for 3.4.1.
Thanks, I can send a patch to implement it. > > > > > I implemented a tool named FuncGraph[1] to convert function_graph > > ftrace output into an interactive HTML file. It leverages fastfaddr2line > > to map return addresses (e.g., __sys_bpf+0x51/0x500) to their > > corresponding call sites, such as: __sys_bpfat kernel/bpf/syscall.c:6115. > > > > What do you think? > > Sounds cool. Is this the vibe coding thing you talked about on Linked-In? Yes. The project repository includes a sample HTML file (`sample.html`) demonstrating the functionality — feel free to try it out. I hope future versions of `trace-cmd` or `Kernelshark` could incorporate similar features to enhance trace analysis workflows. > > -- Steve > > > > > Thanks, > > Donglin > > > > [1] https://github.com/pengdonglin137/FuncGraph > > > > > > > > -- Steve > > > > > > > > > > > > [1] > > > https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/tag/?h=trace-cmd-v3.4 >
