Skip to content
This repository was archived by the owner on Mar 28, 2023. It is now read-only.

[SYCL] Adjust Level Zero tests to queue::wait() changes #631

Merged
merged 2 commits into from
Dec 28, 2021
Merged

[SYCL] Adjust Level Zero tests to queue::wait() changes #631

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9dc7d71
[SYCL] Adjust Level Zero tests to queue::wait() changes
sergey-semenov Dec 17, 2021
77fe019
Merge branch 'intel' into l0wait
sergey-semenov Dec 24, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions SYCL/Plugin/level_zero_batch_event_status.cpp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,8 +28,8 @@
// CHECK-NOT: piEventsWait
// CHECK: ---> piEnqueueKernelLaunch
// CHECK: ZE ---> zeCommandListAppendLaunchKernel
// CHECK: ---> piEventsWait
// Look for close and Execute after piEventsWait
// CHECK: ---> piQueueFinish
// Look for close and Execute after piQueueFinish
// CHECK: ZE ---> zeCommandListClose
// CHECK: ZE ---> zeCommandQueueExecuteCommandLists
// CHECK: ---> piEventGetInfo
Expand Down
10 changes: 5 additions & 5 deletions SYCL/Plugin/level_zero_batch_test.cpp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,10 +32,10 @@
// Expected output is that for batching =1 you will see zeCommandListClose,
// and zeCommandQueueExecuteCommandLists after every piEnqueueKernelLaunch.
// For batching=3 you will see that after 3rd and 6th enqueues, and then after
// piEventsWait. For 5, after 5th piEnqueue, and then after piEventsWait. For
// piQueueFinish. For 5, after 5th piEnqueue, and then after piQueueFinish. For
// 4 you will see these after 4th and 8th Enqueue, and for 8, only after the
// 8th enqueue. And lastly for 9, you will see the Close and Execute calls
// only after the piEventsWait.
// only after the piQueueFinish.
// Since the test does this 3 times, this pattern will repeat 2 more times,
// and then the test will print Test Passed 8 times, once for each kernel
// validation check.
Expand Down Expand Up @@ -86,7 +86,7 @@
// CKB4: ZE ---> zeCommandQueueExecuteCommandLists(
// CKB8: ZE ---> zeCommandListClose(
// CKB8: ZE ---> zeCommandQueueExecuteCommandLists(
// CKALL: ---> piEventsWait(
// CKALL: ---> piQueueFinish(
// CKB3: ZE ---> zeCommandListClose(
// CKB3: ZE ---> zeCommandQueueExecuteCommandLists(
// CKB5: ZE ---> zeCommandListClose(
Expand Down Expand Up @@ -142,7 +142,7 @@
// CKB4: ZE ---> zeCommandQueueExecuteCommandLists(
// CKB8: ZE ---> zeCommandListClose(
// CKB8: ZE ---> zeCommandQueueExecuteCommandLists(
// CKALL: ---> piEventsWait(
// CKALL: ---> piQueueFinish(
// CKB3: ZE ---> zeCommandListClose(
// CKB3: ZE ---> zeCommandQueueExecuteCommandLists(
// CKB5: ZE ---> zeCommandListClose(
Expand Down Expand Up @@ -198,7 +198,7 @@
// CKB4: ZE ---> zeCommandQueueExecuteCommandLists(
// CKB8: ZE ---> zeCommandListClose(
// CKB8: ZE ---> zeCommandQueueExecuteCommandLists(
// CKALL: ---> piEventsWait(
// CKALL: ---> piQueueFinish(
// CKB3: ZE ---> zeCommandListClose(
// CKB3: ZE ---> zeCommandQueueExecuteCommandLists(
// CKB5: ZE ---> zeCommandListClose(
Expand Down