[OpenCL] CHIP_USE_INTEL_USM option fails on Intel CPU driver about chipstar

[pvelesko]

╭─pvelesko@cupcake ~/space/chipStar/main ‹b39011d5●›
╰─$ git bisect good                                                                                                                                                                                                                                                                                                                                                     1 ↵
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[f06b69466f8dc5dd55fb42a639c0e4d3f4d83495] OpenCL: Fix USM indirect flags probably caused issues
╭─pvelesko@cupcake ~/space/chipStar/main ‹f06b6946●›

[pvelesko]

Manually setting CHIP_USE_INTEL_USM=OFF allows the tests to run to completion successfully.

[linehill]

Skipping clSetKernelExecInfo() on USM allocations works too (at least for TestLazyModuleInit, TestLargeGlobalVar, TestGlobalVarInit):

diff --git a/src/backend/OpenCL/CHIPBackendOpenCL.cc b/src/backend/OpenCL/CHIPBackendOpenCL.cc
index eb2de777..ee32a427 100644
--- a/src/backend/OpenCL/CHIPBackendOpenCL.cc
+++ b/src/backend/OpenCL/CHIPBackendOpenCL.cc
@@ -257,6 +257,7 @@ annotateIndirectPointers(const CHIPContextOpenCL &Ctx,
     break;
   case AllocationStrategy::IntelUSM:
     PtrListName = CL_KERNEL_EXEC_INFO_USM_PTRS_INTEL;
+    return nullptr; // DEBUG
     break;
   case AllocationStrategy::BufferDevAddr:
     PtrListName = CL_KERNEL_EXEC_INFO_DEVICE_PTRS_EXT;

It seems that passing anything (valid USM allocations) in CL_KERNEL_EXEC_INFO_USM_PTRS_INTEL lists break kernel launches. A bug in the driver?

[pvelesko]

intel/compute-runtime#748