KEMBAR78
[profiler] update CUDA runtime kernel identification logic by namgyu-youn · Pull Request #157890 · pytorch/pytorch · GitHub
Skip to content

Conversation

@namgyu-youn
Copy link
Contributor

@namgyu-youn namgyu-youn commented Jul 9, 2025

@namgyu-youn namgyu-youn requested a review from sraikund16 as a code owner July 9, 2025 02:46
@pytorch-bot
Copy link

pytorch-bot bot commented Jul 9, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/157890

Note: Links to docs will display an error until the docs builds have been completed.

✅ You can merge normally! (1 Unrelated Failure)

As of commit b0b748d with merge base ee72338 (image):

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@namgyu-youn
Copy link
Contributor Author

@pytorchbot label "release notes: profiler"

@pytorch-bot pytorch-bot bot added the release notes: profiler release notes category label Jul 9, 2025

name = str(getattr(e, "name", e)).lower()
# Exclude launcher and memory events
exclude_patterns = ["cudalaunch", "cudamem"]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if this is necessary. cudalaunch will already have DeviceType.CPU. I think we should just check if kernel is in the name...

Copy link
Contributor Author

@namgyu-youn namgyu-youn Jul 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I misunderstood it due to my lack of background. Then how about keeping the current structure and removing #TODO? (cc @davidchencsl )

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think until we can procedurally determine it is a kernel besides looking at the name we should keep the todo

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sraikund16 Thanks for your review. For focusing on excluding memory kernel, I updated for more edge-cases in this commit. Could you take a look at this PR?

@mikaylagawarecki mikaylagawarecki added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Jul 14, 2025
@namgyu-youn namgyu-youn marked this pull request as draft July 15, 2025 03:30
@namgyu-youn namgyu-youn marked this pull request as ready for review July 15, 2025 10:14
@namgyu-youn namgyu-youn requested a review from sraikund16 July 15, 2025 10:14
@sraikund16
Copy link
Contributor

@pytorchbot rebase

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

Use cases:
- "mem" : "cudaMemcpy", "cudaMemset"
- "alloc" : "cudaMalloc", "cudaMallocManaged"
- "free" : "cudaFree"
@pytorchmergebot
Copy link
Collaborator

Successfully rebased profiler_kernel onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout profiler_kernel && git pull --rebase)

@namgyu-youn
Copy link
Contributor Author

@pytorchbot merge

@pytorch-bot
Copy link

pytorch-bot bot commented Jul 24, 2025

Pull workflow has not been scheduled for the PR yet. It could be because author doesn't have permissions to run those or skip-checks keywords were added to PR/commits, aborting merge. Please get/give approval for the workflows and/or remove skip ci decorators before next merge attempt. If you think this is a mistake, please contact PyTorch Dev Infra.

@namgyu-youn
Copy link
Contributor Author

@pytorchmergebot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Jul 24, 2025
@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/trunk Trigger trunk jobs on your pull request Merged open source release notes: profiler release notes category triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants