Skip to content

[UR][CUDA] Use different throttle reasons API based on CUDA version #17719

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

Merged
merged 1 commit into from
Mar 31, 2025

Conversation

againull
Copy link
Contributor

Our pre-commit CI uses CUDA 12.6 but nightly uses CUDA 12.1, it turns out nvml which is part of CUDA 12.6 has nvmlDeviceGetCurrentClocksEventReasons API, but nvml which is part of CUDA 12.1 doesn't have it, but only supports older deprecated nvmlDeviceGetCurrentClocksThrottleReasons.

NVML doesn't provide a version macro to check the support for that API, so use new API nvmlDeviceGetCurrentClocksEventReasons based on cuda version.

Our pre-commit CI uses CUDA 12.6 but nightly uses CUDA 12.1, it turns
out nvml which is part of CUDA 12.6 has nvmlDeviceGetCurrentClocksEventReasons
API, but nvml which is part of CUDA 12.1 doesn't have it, but only
supports older deprecated nvmlDeviceGetCurrentClocksThrottleReasons.

NVML doesn't provide a version macro to check the support for that API, so
use new API nvmlDeviceGetCurrentClocksEventReasons based on cuda version.
@againull againull requested a review from a team as a code owner March 28, 2025 19:33
@againull againull requested a review from omarahmed1111 March 28, 2025 19:33
@againull
Copy link
Contributor Author

Jenkins/Precommit failure is unrelated and visible in other PRs.

@againull againull merged commit cf1a3d3 into intel:sycl Mar 31, 2025
31 of 32 checks passed
KornevNikita pushed a commit that referenced this pull request Jun 4, 2025
…17719)

Our pre-commit CI uses CUDA 12.6 but nightly uses CUDA 12.1, it turns
out nvml which is part of CUDA 12.6 has
nvmlDeviceGetCurrentClocksEventReasons API, but nvml which is part of
CUDA 12.1 doesn't have it, but only supports older deprecated
nvmlDeviceGetCurrentClocksThrottleReasons.

NVML doesn't provide a version macro to check the support for that API,
so use new API nvmlDeviceGetCurrentClocksEventReasons based on cuda
version.
KornevNikita pushed a commit that referenced this pull request Jun 12, 2025
…17719)

Our pre-commit CI uses CUDA 12.6 but nightly uses CUDA 12.1, it turns
out nvml which is part of CUDA 12.6 has
nvmlDeviceGetCurrentClocksEventReasons API, but nvml which is part of
CUDA 12.1 doesn't have it, but only supports older deprecated
nvmlDeviceGetCurrentClocksThrottleReasons.

NVML doesn't provide a version macro to check the support for that API,
so use new API nvmlDeviceGetCurrentClocksEventReasons based on cuda
version.
AlexeySachkov pushed a commit that referenced this pull request Jun 18, 2025
Cherry-pick commits that reached the internal branch between intel/llvm
cutoff and release branch pulldown.

Patches included:

---

[SYCL][Doc] Add new device descriptors to sycl_ext_intel_device_info extension (#17386)

Patch-by: Artur Gainullin <[email protected]>

---

[SYCL][CUDA] Add implementation of new device descriptors (#17590)

Tests were not added because there are existing conformance tests which
cover this functionality.

Patch-by: Artur Gainullin <[email protected]>

---

[UR][CUDA] Use different throttle reasons API based on CUDA version (#17719)

Our pre-commit CI uses CUDA 12.6 but nightly uses CUDA 12.1, it turns
out nvml which is part of CUDA 12.6 has
nvmlDeviceGetCurrentClocksEventReasons API, but nvml which is part of
CUDA 12.1 doesn't have it, but only supports older deprecated
nvmlDeviceGetCurrentClocksThrottleReasons.

NVML doesn't provide a version macro to check the support for that API,
so use new API nvmlDeviceGetCurrentClocksEventReasons based on cuda
version.

Patch-by: Artur Gainullin <[email protected]>
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.

2 participants