vllm - 💡(How to fix) Fix [vLLM IR] Propagate IR op names to torch profiler annotations [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vllm-project/vllm#39363Fetched 2026-04-09 07:51:34
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Participants
Timeline (top)
added_to_project_v2 ×1mentioned ×1project_v2_item_status_changed ×1subscribed ×1
RAW_BUFFERClick to expand / collapse

Looking at a torch profile (or nsys), it can often be difficult to know which kernel appearing in the profile correspond to which semantic operation. It would be good if we could somehow propagate this information down, specifically annotating both custom and codegen-ed Triton kernels with the corresponding IR op (and implementation name). This is slightly related to #39215.

(thanks @tlrmchlsmth for the idea!)

extent analysis

TL;DR

Annotating custom and codegen-ed Triton kernels with corresponding IR op and implementation name can improve the readability of torch profiles.

Guidance

  • Identify the source of kernel generation to determine where annotations can be added, potentially in the codegen process or when creating custom kernels.
  • Investigate existing profiling tools like nsys for any built-in features or APIs that support custom annotations.
  • Review related issues like #39215 for potential insights or partial solutions that could be adapted.
  • Consider modifying the kernel creation process to include metadata about the corresponding IR operation and implementation name.

Example

No specific code example can be provided without more context on the kernel generation process.

Notes

The feasibility of annotating kernels may depend on the specific implementation details of the torch profiling tool and the Triton kernel generation process, which are not provided in the issue.

Recommendation

Apply workaround: Modify the kernel creation process to include annotations, as this seems to be a targeted solution to the problem of identifying kernel operations in profiles.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING