Modify USM device allocation information returned by clGetDeviceInfo #286
Conversation
This file contains 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
According to USM extension spec, clDeviceMemAllocINTEL will return NULL and CL_INVALID_OPERATION status if the device has property CL_DEVICE_DEVICE_MEM_CAPABILITIES_INTEL equal to 0. Before, the runtime always return 1 for device allocation capabilities as all legacy devices support device allocations. This is no longer true in IP Authoring flow.
zibaiwan
approved these changes
Apr 12, 2023
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.
According to USM extension spec, clDeviceMemAllocINTEL will return
NULLandCL_INVALID_OPERATIONstatus if the device has propertyCL_DEVICE_DEVICE_MEM_CAPABILITIES_INTELequal to 0. Before, the runtime always return 1 for device allocation capabilities as all legacy devices support device allocations. This is no longer true in IP Authoring flow.