Skip to content

Conversation

@rsavitski
Copy link
Member

@rsavitski rsavitski commented Oct 10, 2025

We're currently moving all thread-scoped tracks into the "Kernel
threads" group, but are abandoning the process-scoped tracks. This patch
addresses that by adjusting ProcessThreadGroups.

While there, simplify the kthread query since there's a viz analog,
and remove the always-empty summary track (which makes the group track
thin, but I think that's fine).

This came up for traces containing perf samples + procfs trees, but no
sched_switch to supply thread names. The result is that the grouped
kernel thread tracks end up mostly anonymous (since the procfs scraping
is only supplying the process names). Additionally, a subset of those
threads does end up with a name due to the trace including "task_rename"
ftrace events.

On modern traces, we actually know if the "cmdline" field in the trace
was set from /proc/pid/comm, so we can use that information to name the
main thread as well.
@rsavitski rsavitski force-pushed the dev/rsavitski/perf-process-group branch from 28ead99 to b5dd331 Compare October 15, 2025 20:13
@rsavitski rsavitski changed the title wip: group process-level tracks for kernel threads ui: group kthread process tracks in addition to thread tracks Oct 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants