Skip to content

[SYCL][DOC] Updates to sycl_ext_oneapi_reusable_events specification.#22201

Merged
KornevNikita merged 5 commits into
intel:syclfrom
slawekptak:ext_reusable_events_p2p_requirement_remove
Jun 23, 2026
Merged

[SYCL][DOC] Updates to sycl_ext_oneapi_reusable_events specification.#22201
KornevNikita merged 5 commits into
intel:syclfrom
slawekptak:ext_reusable_events_p2p_requirement_remove

Conversation

@slawekptak

@slawekptak slawekptak commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

List of changes:

  • Counter based events can be enqueued for signaling on any device in the system, so there is no requirement for P2P access between devices.
  • The device argument is not required for make_event, since the event is associated with a device on the first call to enqueue_signal_event. Which device is associated with an event (if any) right after the make_event call is implementation specific.
  • A new device aspect for reusable events (since this extension might not be supported on all backends).

@slawekptak
slawekptak requested review from Copilot and gmlueck June 3, 2026 12:08
@slawekptak
slawekptak requested a review from a team as a code owner June 3, 2026 12:08

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the proposed sycl_ext_oneapi_reusable_events extension specification to reflect that counter-based events may be enqueued for signaling on any device in the system, removing the previously documented requirement for P2P accessibility between the event’s device and the queue’s device.

Changes:

  • Removed the documented _Throws_ condition that required P2P access (and referenced ext_oneapi_can_access_peer / ext_oneapi_enable_peer_access) when evt and q were associated with different devices.
  • Keeps the enqueue_signal_event behavior consistent with the rest of the document’s cross-device/cross-context event usage remarks.

Counter based events can be enqueued for signaling on any device
in the system, so there is no requirement for P2P access between
devices.
@slawekptak slawekptak changed the title [SYCL][DOC] Remove the P2P-related requirement from enqueue_signal_event [SYCL][DOC] Updates to sycl_ext_oneapi_reusable_events. Jun 16, 2026
@slawekptak slawekptak changed the title [SYCL][DOC] Updates to sycl_ext_oneapi_reusable_events. [SYCL][DOC] Updates to sycl_ext_oneapi_reusable_events specification. Jun 16, 2026
Comment thread sycl/doc/extensions/proposed/sycl_ext_oneapi_reusable_events.asciidoc Outdated
@slawekptak
slawekptak requested a review from againull June 18, 2026 14:40
Comment thread sycl/doc/extensions/proposed/sycl_ext_oneapi_reusable_events.asciidoc Outdated
Comment thread sycl/doc/extensions/proposed/sycl_ext_oneapi_reusable_events.asciidoc Outdated
@slawekptak

Copy link
Copy Markdown
Contributor Author

@intel/llvm-gatekeepers please consider merging

@KornevNikita
KornevNikita merged commit 67e9b02 into intel:sycl Jun 23, 2026
4 checks passed
wenju-he pushed a commit that referenced this pull request Jun 26, 2026
…#22201)

List of changes:
- Counter based events can be enqueued for signaling on any device in
the system, so there is no requirement for P2P access between devices.
- The `device` argument is not required for make_event, since the event
is associated with a device on the first call to enqueue_signal_event.
Which device is associated with an event (if any) right after the
make_event call is implementation specific.
- A new device aspect for reusable events (since this extension might
not be supported on all backends).
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.

5 participants