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 mechanism to specify named win32 NT handles #1177

Merged
merged 8 commits into from
Sep 3, 2024

Conversation

nikhiljnv
Copy link
Contributor

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 NT handles via named strings too.

Fixes #943

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 NT handles via named strings too.

Fixes #943
Comment on lines +1897 to +1898
<enum value="0x2068" name="CL_SEMAPHORE_HANDLE_OPAQUE_WIN32_NAME_KHR"/>
<enum value="0x2069" name="CL_EXTERNAL_MEMORY_HANDLE_OPAQUE_WIN32_NAME_KHR"/>
Copy link
Contributor

Choose a reason for hiding this comment

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

I think these should also be added to the <extension name="cl_khr_external_memory_win32" block below, to associate them with this extension.

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.

One more comment, sorry: I think this needs to bump the extension version also, probably to v1.1?

* Updates to win32 named handle type changes.

Address review comments.

Fixes #943

* Drop NULL from named win32 handle description.

Address review comments from Ben to remove NULL
from named win32 handle description.

Fixes #943
@bashbaug
Copy link
Contributor

Reviewed in the June 18th memory TSG.

The updated text looks good.
The extension version needs to be updated in the XML file.
It would also be good to do a rebase or merge to pick up the latest XML changes.

nikhiljnv and others added 3 commits June 27, 2024 10:54
Bump up spec versions for
cl_khr_external_memory_win32 from 1.0.0 to 1.1.0
and cl_khr_external_semaphore_win32 from 0.9.0 to 0.9.1
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.

My changes have been addressed - thanks!

Note, I did fix one small typo, and added CL_SEMAPHORE_HANDLE_OPAQUE_WIN32_NAME_KHR to the list of new enums for cl_khr_external_semaphore_win32.

@bashbaug
Copy link
Contributor

bashbaug commented Sep 3, 2024

Merging as discussed in the September 3rd teleconference.

@bashbaug bashbaug merged commit d83f47b into main Sep 3, 2024
3 checks passed
@bashbaug bashbaug deleted the external_memory_win32_name_handle branch September 3, 2024 17:05
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.

Importing external memory via named NT handle reference along with pointer reference
3 participants