Skip to content

mutable dispatch related fixes#2143

Open
franz wants to merge 3 commits intoKhronosGroup:mainfrom
franz:mutable_dispatch_fixes
Open

mutable dispatch related fixes#2143
franz wants to merge 3 commits intoKhronosGroup:mainfrom
franz:mutable_dispatch_fixes

Conversation

@franz
Copy link
Contributor

@franz franz commented Nov 6, 2024

No description provided.

@franz franz force-pushed the mutable_dispatch_fixes branch from c26f9eb to 2cdd0eb Compare November 6, 2024 19:00
franz and others added 3 commits November 27, 2024 16:54
…heck

the test checks 'cl_khr_extended_versioning' then immediately calls:
get_extension_version(device, "cl_khr_command_buffer_mutable_dispatch");
.. however, get_extension_version throws an exception when called
with unsupported extension.
the test uses CL_MUTABLE_DISPATCH_ARGUMENTS_KHR,
but does not check for support.
test MutableDispatchGlobalSize was failing (with an implementation that
doesn't support non-uniform WGs), because the update_global_size = 3
was not a multiple of the local work-size.

Fixed by increasing the global work-size to 256K and update size to 16K.
This should work with all devices that have max_work_group_size <= 16K.

Updates also MutableDispatchWorkGroups which had an out-of-bounds access,
because it hardcoded the value of global work-size.
@franz franz force-pushed the mutable_dispatch_fixes branch from 2cdd0eb to a2fc5d8 Compare November 27, 2024 14:54
@franz franz requested a review from EwanC November 27, 2024 15:53
Copy link
Contributor

@EwanC EwanC left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry it's taken me a while to re-review this.

My main thought from looking at this again is whether we need to be using as many as 256K and 16K work items for the test, which is quite a big increase on what we had before. I'm not sure if on embedded devices or simulators that would slow the test time down and not really give us that much extra testing coverage of the extension. Could we use work item sizes that are an order of magnitude less but still resolve the issues you've seen?

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