[UR] Add IPC event-sharing API to inter-process communication extension#22366
Open
againull wants to merge 3 commits into
Open
[UR] Add IPC event-sharing API to inter-process communication extension#22366againull wants to merge 3 commits into
againull wants to merge 3 commits into
Conversation
Define UR APIs for sharing event objects between processes.
* Added the IPC_EVENT_SUPPORT_EXP device info query.
* Extended ur_exp_event_flags_t (from the reusable events extension) with
UR_EXP_EVENT_FLAG_IPC_EXP, requested via ur_exp_event_desc_t::flags at
urEventCreateExp time so SYCL's enable_ipc property can be expressed.
* Added urIPCGetEventHandleExp / urIPCPutEventHandleExp /
urIPCOpenEventHandleExp.
Sharing is bidirectional: an event opened with urIPCOpenEventHandleExp shares
state with the source event, so a state change made through either event is
observable through the other and either event can be signaled, waited on, or
queried. Events created with profiling/timestamping enabled cannot be shared.
The event returned by urIPCOpenEventHandleExp is a normal ur_event_handle_t
released through urEventRelease; there is no separate IPC event close entry
point. Although Level Zero exposes zeEventCounterBasedCloseIpcHandle, a dedicated
UR close API would add a second public release path for the same handle and
break the uniform reference-counted lifetime of UR events. The adapter instead
records that the event was opened from an IPC handle and, on the final
urEventRelease, selects the IPC-specific native teardown rather than the normal
event cleanup path.
This commit updates only the yml definitions and rst documentation.
Assisted-By: Claude
pbalcer
approved these changes
Jun 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Define UR APIs for sharing event objects between processes.
UR_EXP_EVENT_FLAG_IPC_EXP, requested via ur_exp_event_desc_t::flags at
urEventCreateExp time so SYCL's enable_ipc property can be expressed.
urIPCOpenEventHandleExp.
Sharing is bidirectional: an event opened with urIPCOpenEventHandleExp shares
state with the source event, so a state change made through either event is
observable through the other and either event can be signaled, waited on, or
queried. Events created with profiling/timestamping enabled cannot be shared.
The event returned by urIPCOpenEventHandleExp is a normal ur_event_handle_t
released through urEventRelease; there is no separate IPC event close entry
point. Although Level Zero exposes zeEventCounterBasedCloseIpcHandle, a dedicated
UR close API would add a second public release path for the same handle and
break the uniform reference-counted lifetime of UR events. The adapter instead
records that the event was opened from an IPC handle and, on the final
urEventRelease, selects the IPC-specific native teardown rather than the normal
event cleanup path.
Assisted-By: Claude