[UR][CI] Update to v1.25.2 L0 with fixed L0 api symbols #20537
+17
−18
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
nrspruit
had a problem deploying
to
WindowsCILock
GitHub Actions
Error
nrspruit
force-pushed
the
test_1_25_L0
branch
from
22512b8 to
4e78a1c
Compare
nrspruit
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
nrspruit
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
nrspruit
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
nrspruit
force-pushed
the
test_1_25_L0
branch
from
4e78a1c to
9a664ee
Compare
nrspruit
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
nrspruit
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
nrspruit
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
nrspruit
force-pushed
the
test_1_25_L0
branch
from
9a664ee to
84e351f
Compare
nrspruit
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
nrspruit
had a problem deploying
to
WindowsCILock
GitHub Actions
Error
nrspruit
had a problem deploying
to
WindowsCILock
GitHub Actions
Failure
nrspruit
force-pushed
the
test_1_25_L0
branch
from
84e351f to
1f4dc3d
Compare
nrspruit
had a problem deploying
to
WindowsCILock
GitHub Actions
Error
nrspruit
force-pushed
the
test_1_25_L0
branch
from
1f4dc3d to
6817bf4
Compare
nrspruit
had a problem deploying
to
WindowsCILock
GitHub Actions
Error
nrspruit
force-pushed
the
test_1_25_L0
branch
from
6817bf4 to
42c4cf8
Compare
nrspruit
changed the title
nrspruit
had a problem deploying
to
WindowsCILock
GitHub Actions
Error
nrspruit
force-pushed
the
test_1_25_L0
branch
from
42c4cf8 to
16f7816
Compare
nrspruit
had a problem deploying
to
WindowsCILock
GitHub Actions
Error
- Due to symbol conflicts in the L0 gpu driver, zeCommandListAppendLaunchKernelWithArguments can only be used from the spec definition and the driver exp cannot be used as of the update to v1.14 supported symbols. Signed-off-by: Neil R. Spruit <neil.r.spruit@intel.com>
nrspruit
force-pushed
the
test_1_25_L0
branch
from
16f7816 to
e777ffb
Compare
nrspruit
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
nrspruit
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
nrspruit
had a problem deploying
to
WindowsCILock
GitHub Actions
Failure
nrspruit
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
ldorau
reviewed
Nov 4, 2025
| zeCommandListAppendLaunchKernelWithArguments; | ||
| ZeCommandListAppendLaunchKernelWithArgumentsExt.Supported = true; | ||
| } else { | ||
| ZeCommandListAppendLaunchKernelWithArgumentsExt.Supported = false; |
There was a problem hiding this comment.
@nrspruit Why cannot zeCommandListAppendLaunchKernelWithArgumentsFunctionPtr be read using zeDriverGetExtensionFunctionAddress() in case of older drivers as it was before?
There was a problem hiding this comment.
Unfortunately, because the driver exp version of zeCommandListAppendLaunchKernelWithArguments is named the same as the spec version, the driver was reporting the loader's symbol instead of its own once v1.14 L0 supported loader is loaded into the application, thus returning the "unsupported" version of the api in that driver. So, the existence of the new loader in the system exposes the bug in the driver. The bug in the driver has been fixed, but by the time the fix for this issue will be in a driver in the CI, then the driver EXP function will no longer be supported and is replaced by the L0 spec function, which is what I changed this to use.
Therefore, we cannot report support for that api in the UR V2 adapter until one has a new enough driver with the fix:
intel/compute-runtime@c92ab7c
Which will also include the support for the L0 spec api.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
No description provided.