Re: [PATCH perf-tools-next v2 0/4] perf trace: Symbolise kernel virtual addresses and function pointers

On Mon, Aug 17, 2026 at 03:52:07PM -0700, Ian Rogers wrote:
> On Sun, Aug 16, 2026 at 1:59 PM Aaron Tomlin <[email protected]> wrote:
> >
> > When inspecting kernel execution flows using perf trace (e.g., when
> > monitoring workqueues delayed work items, timer callbacks, etc.),
> > tracepoint payload arguments containing raw kernel virtual addresses are
> > currently rendered as hexadecimal values (e.g., 0xffffffff81234567).
> >
> > This requires manual symbol lookups against /proc/kallsyms or vmlinux to
> > identify the underlying kernel function being executed.
> >
> > This patch series enhances perf trace by introducing kernel virtual
> > address and function pointer symbolisation using perfs native symbol
> > engine (i.e., machine__find_kernel_symbol()).
> >
> >     Before:
> >       workqueue:workqueue_execute_end(work: 0xffffffffab2f1420, function: 0xffffffffa8046b50)
> >
> >     After:
> >       workqueue:workqueue_execute_end(work: 0xffff8ac2c420f270, function: wb_update_bandwidth_workfn)
> 
> This looks great and a test! I noticed Sashiko feedback on patches 2,
> 3 and 4. It looked appropriate and actionable. I'm looking forward to
> the next version and testing!
> 
> Thanks,
> Ian

Hi Ian,

Thank you!

Kind regards,
-- 
Aaron Tomlin