[UR] Fix usm pools creation failure at context initialization #20054
+56
−10
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.
This is a cherry-pick of #19921
Context creation was failing when sub-sub-devices were exposed, because the Level Zero adapter attempted to add multiple USM pools with identical descriptors. This occurred since, for the L0 backend, sub-sub-devices and their parent sub-devices share the same Level Zero device handle and should use the same USM pool.
This PR resolves the issue by ensuring only devices with unique Level Zero
handles are collected for USM pool creation, preventing duplicate pools.
Additionally, this PR fixes an issue with an uninitialized
ur_device_partition_property_t
variable passed to UR. Previously, this could result in an unexpected value forvalue.affinity_domain
when the property type wasUR_DEVICE_PARTITION_BY_CSLICE
resulting on error fromadapter.