-
Notifications
You must be signed in to change notification settings - Fork 217
Introduce XPU scope profiler extending existing XPU profiler plugin #1174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
@moksiuc It's great that we are going to update our PTI integration code, and introduce new profiler path.
|
|
For sure not in this PR. I'll add this to our list of tasks. |
Extracted clean up and adding config for scope profiler to separate PR's. |
- place of config initialization - removal of passing unused C compiler flag into test cmake file
gujinghui
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
@moksiuc Let's close this PR. |
|
@gujinghui this is the core of the scope profiler. When 2 smaller parts are merged this one would have only core profiler left. |
Otherwise old profiler requires setting ZET_ENABLE_METRICS what is incorrect requirement.
|
@EikanWang, @gujinghui |
|
Tests are run on pytorch part: |
| scopeProfilerEnabled = true; | ||
| #else | ||
| throw std::runtime_error( | ||
| "Intel® oneAPI version required to use scope profiler is at least 2025.3.1"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we give the PTI version here, instead of oneAPI package version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had previously PTI version but is it not clearer for the user to have one api version ?
Has the user possibility to install any PTI version he wants ?
| @@ -0,0 +1,55 @@ | |||
| # Copyright (c) Meta Platforms, Inc. and affiliates. | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@chuanqi129 If we want to append these cases in XPU CI scope, how should we do?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @gujinghui , we don't have xpu ci test for kineto repo, do you mean put those test cases into stock pytorch? If so, we may evaluate whether can put them into https://github.com/pytorch/pytorch/tree/main/test/cpp/profiler
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes. @moksiuc please sync with @chuanqi129 to make it. Thanks.
gujinghui
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I assume you already verified it on local real machine, right? @moksiuc
Yes, I did. |
|
@sraikund16 could you help review this PR? Thanks. |
Summary:
As XPU became a PyTorch built-in device, the profiler support is indispensable part of functionality completeness. In this PR, the XPU scope profiler is introduced by extending existing XPU profiler plugin. The XPU scope profiler is built on the foundation of intel PTI toolkit (https://github.com/intel/pti-gpu), and underlying SYCL runtime. It allows to gather XPU hardware metrics. The LIBKINETO_NOXPUPTI option is used to enable or disable the whole XPU profiler plugin during kineto build stage.
Changes: