Skip to content

fix: ops_summary shows GPU kernel names for orphan HIP launches (#641)#642

Open
gabeweisz wants to merge 4 commits into
mainfrom
fix/ops-summary-hip-kernel-names-641
Open

fix: ops_summary shows GPU kernel names for orphan HIP launches (#641)#642
gabeweisz wants to merge 4 commits into
mainfrom
fix/ops-summary-hip-kernel-names-641

Conversation

@gabeweisz

Copy link
Copy Markdown
Collaborator

Summary

Fixes #641.

When GPU work is launched from a standalone hipLaunchKernel (or other cuda_runtime/cuda_driver) row with no cpu_op ancestor, ops_summary grouped every such launch under the same name. The DataFrame now uses the actual kernel name(s) from kernel_details, consistent with unified perf synthetic naming.

Changes

  • TreePerfAnalyzer._kernel_launcher_ops_summary_name: for cuda_runtime / cuda_driver launchers with kernel_details, set the row name to the kernel name (comma-separated if multiple).
  • Tests: orphan launcher row name, mixed linked/unlinked DataFrame names, two orphans produce two ops_summary rows.

Testing

pytest tests/test_kernel_launchers.py (21 passed).

Made with Cursor

When no cpu_op ancestor exists, the launcher row is cuda_runtime
(hipLaunchKernel). ops_summary grouped by that name, merging distinct
custom kernels. Substitute kernel name(s) from kernel_details for
cuda_runtime/cuda_driver launchers, matching unified perf behavior.

Fixes #641

Co-authored-by: Cursor <cursoragent@cursor.com>
@gabeweisz gabeweisz requested review from a team and ajassani as code owners May 14, 2026 13:48
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.

Ops_summary report should show the full kernel name for custom HIP kernels

1 participant