Move XPUEvent to c10 #158336
Open
Move XPUEvent to c10 #158336
+191
−189
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/158336
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit fe221f5 with merge base b1a6027 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This was referenced Jul 15, 2025
guangyey
commented
Jul 15, 2025
| @@ -1,191 +1,3 @@ | |||
| #pragma once | |||
| #include <ATen/xpu/XPUContext.h> | |||
|
|
|||
| #include <optional> | |||
There was a problem hiding this comment.
Already included in <ATen/xpu/XPUContext.h>
EikanWang
approved these changes
Aug 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Stack from ghstack (oldest at bottom):
Motivation
Move
XPUEventtoc10/xputo keep consistent withXPUStream, which is already inc10/xpu. The most important thing is that we will leverageXPUEvent in our caching allocator instead of a raw sycl event.