Skip to content
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

Add global size tests for cl_khr_command_buffer_mutable_dispatch. #1744

Merged
merged 10 commits into from
Jul 11, 2023

Conversation

pj87
Copy link
Contributor

@pj87 pj87 commented May 26, 2023

No description provided.

We should check that's some observable output from the kernel
as a result of the change to global work size, not just that
clGetMutableCommandInfoKHR has been updated. For example,
getting every work-item to call get_global_size() inside of
the kernel and writing it to a buffer, then reading the buffer
after the command-buffer enqueue has finished and check it
matches what we expect.

Signed-off-by: Paweł Jastrzębski <[email protected]>
pj87 added 3 commits June 1, 2023 11:22
Applied review comments for mutable dispatch global arguments test:
- clFinish to ensure command-buffer has finished executing for calling clUpdateMutableCommandsKHR
- Change variable and constant names for global size

Signed-off-by: Paweł Jastrzębski <[email protected]>
Changes made:
- Fix skip conditions
- Remove obsolete variable
- Replace a variable with a constant

Signed-off-by: Paweł Jastrzębski <[email protected]>
Copy link
Contributor

@bashbaug bashbaug left a comment

Choose a reason for hiding this comment

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

Please also see my comments on #1743, many of which apply here.

(Some of these comments may apply to #1743 also!)

Comment on lines 171 to 174
size_t info_global_size = 0;
const size_t update_global_size = 3;
const size_t sizeToAllocate = 64;
const size_t num_elements = sizeToAllocate / sizeof(cl_int);
Copy link
Contributor

Choose a reason for hiding this comment

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

Nitpick: I think these variables are only used inside of Run - do they need to be class member variables?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I decided to put it there for more tidy code, since they are mostly consts.

pj87 added 2 commits June 14, 2023 10:05
Changes made:
- Remove explicit base class call
- Fix condition check
- Fix constant magic number

Signed-off-by: Paweł Jastrzębski <[email protected]>
Signed-off-by: Paweł Jastrzębski <[email protected]>
EwanC
EwanC previously approved these changes Jun 27, 2023
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.

Needs rebased to remove conflicts, but happy with test content.

Signed-off-by: Paweł Jastrzębski <[email protected]>
EwanC
EwanC previously approved these changes Jul 3, 2023
Copy link
Contributor

@bashbaug bashbaug left a comment

Choose a reason for hiding this comment

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

Merging as discussed in the July 11th teleconference.

@bashbaug bashbaug merged commit 6413082 into KhronosGroup:main Jul 11, 2023
6 checks passed
@pj87 pj87 deleted the Mutable-commands-global-size branch November 10, 2023 18:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants