Nikhil Joshi

OpenCL-Header versioning

1

Currently OpenCL headers are versioned based on the OpenCL spec (1.2, 2.0, 2.2 etc) Apart from the core and optional core features that we change only with OpenCL version, we...

Fix test_vulkan to allow running it on any platform and VkDevice rather than platform 0, device 0. Use test_harness for common functionality for choosing platform and device.

Some cl_khr_external_sync_fd related tests are currently present in cl_khr_semaphore. https://github.com/KhronosGroup/OpenCL-CTS/blob/f924273cdd607db39e8ff5e1490f5cef87242b7e/test_conformance/extensions/cl_khr_semaphore/test_semaphores.cpp#L651C80-L651C80 May be move these to a separate directory specific to cl_khr_external_sync_fd or cl_khr_external_semaphore at least.

Test coverage for CL_SEMAPHORE_HANDLE_LIST_KHR as part of cl_khr_semaphore tests

1

https://github.com/KhronosGroup/OpenCL-CTS/pull/1814 added minimal coverage for CL_MEM_HANDLE_LIST_KHR and CL_SEMAPHORE_HANDLE_LIST_KHR to external memory and external semaphore tests. We need to cover CL_SEMAPHORE_HANDLE_LIST_KHR as part of cl_khr_semaphore tests as well. In particular, we...

WIP: Add CONTRIBUTING.md and explain version increment

2

Add CONTRIBUTING.md to explain 1. How to contribute to OpenCL ICD Loader project. 2. ICD loader versioning guidelines including when to increment the version number.

Add mechanism to specify named win32 NT handles.

1

Currently, cl_khr_external_semaphore and cl_khr_external_memory define properties to specify external win32 NT handle via pointer. Win32 NT handles can also be specified via named strings. Add properties to specify external Win32...

Clarify behavior in case of multiple clEnqueueAcquireExternalMemObjectsKHR calls on the same cl_mem

3

Clarify behavior in case of multiple clEnqueueAcquireExternalMemObjectsKHR calls on the same cl_mem without corresponding clEnqueueReleaseExternalMemObjectsKHR. This came up as part of https://github.com/KhronosGroup/OpenCL-CTS/pull/1899

Clarify the scope of clEnqueueAcquireExternalMemObjectsKHR and clEnqueueReleaseExternalMemObjectsKHR

1

The spec doesn't say clearly if the acquire and release calls are supposed to be applicable for external memobj usage across command queues, devices of the context or are limited...

[cl_khr_external_memory ](https://registry.khronos.org/OpenCL/specs/3.0-unified/html/OpenCL_Ext.html#cl_khr_external_memory) allows importing external memory specified via NT handle through CL_EXTERNAL_MEMORY_HANDLE_OPAQUE_WIN32_KHR The spec says "CL_EXTERNAL_MEMORY_HANDLE_OPAQUE_WIN32_KHR specifies an NT handle ..." This is mostly assuming reference to external memory is...

Add mechanism to specify named win32 NT handles

1

Currently, cl_khr_external_semaphore and cl_khr_external_memory define properties to specify external win32 NT handle via pointer. Win32 NT handles can also be specified via named strings. Add properties to specify external Win32...