Skip to content

Conversation

KonstantyMisiak
Copy link
Contributor

No description provided.

@KonstantyMisiak

This comment was marked as outdated.

@marekkozl
Copy link
Contributor

Convert to draft if in progress

@KonstantyMisiak KonstantyMisiak marked this pull request as draft August 27, 2025 07:46
@KonstantyMisiak KonstantyMisiak marked this pull request as ready for review August 27, 2025 12:44
Copy link
Contributor

@gwawiork gwawiork left a comment

Choose a reason for hiding this comment

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

Minor changes please fix

@@ -24,6 +24,7 @@ add_lzt_test(
level_zero_tests::random
${OS_SPECIFIC_LIBS}
KERNELS
cooperative_kernel
Copy link
Contributor

Choose a reason for hiding this comment

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

Update header entry to 2019-2025


ze_module_handle_t module =
lzt::create_module(device, "cooperative_kernel.spv");
const char *funcion_name =
Copy link
Contributor

Choose a reason for hiding this comment

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

Typo should be function_name

__kernel void cooperative_kernel(__global int* input, __global int* output, const int N) {
const int gid = get_global_id(0);

barrier(CLK_LOCAL_MEM_FENCE | CLK_GLOBAL_MEM_FENCE);
Copy link
Contributor

Choose a reason for hiding this comment

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

Why do you use barriers in both kernels? There is no race condition in this scenario.

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.

4 participants