-
Notifications
You must be signed in to change notification settings - Fork 124
[UR][hip][opencl] Mark urKernelSuggestMaxCooperativeGroupCountExp as unsupported instead of returning misleading default value #2038
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
Conversation
frasercrmck
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.
Makes sense to me
609cae5 to
6eb27d5
Compare
ca55cef to
73ca483
Compare
fa515a0 to
ed6fbad
Compare
…unsupported instead of returning misleading default value
ed6fbad to
55bd563
Compare
…xceeded launch limits on more backends (hip and opencl) (#15369) The HIP and OpenCL backend implementations of the query had a default return `1` group implementation, which is an incorrect assumptions. They will now be marked as _Unsupported_ with the accompanying UR chagnes (see oneapi-src/unified-runtime#2038), so for these cases the `kernel_queue_specific::max_num_work_groups` launch query will rely on the fallback that returns either `1` or `0` groups based on hardware resource limitation checks for the kernel. --------- Co-authored-by: Aaron Greig <[email protected]>
|
@GeorgeWeb |
|
What about the following function for HIP ? |
Hi @jinz2014. You are more than welcome to open a Github issue for the team in case they may have the bandwidth for this or straight up a PR request for HIP with the implementation you suggested in your other comment. Thank you for being proactive on the project! |
intel/llvm: intel/llvm#15369