Repository navigation
[FEA]: Support CU_LAUNCH_ATTRIBUTE_PROGRAMMATIC_EVENT in LaunchConfig #2630
Description
Is this a duplicate?
- I confirmed there appear to be no duplicate issues for this request and that I agree to the Code of Conduct
Area
cuda.core
Is your feature request related to a problem? Please describe.
LaunchConfig does not expose CU_LAUNCH_ATTRIBUTE_PROGRAMMATIC_EVENT, which records a programmatic event for cross-stream PDL (complements same-stream programmatic_stream_serialization from #1334).
Parent tracking: #496.
Describe the solution you'd like
- Users can set
CU_LAUNCH_ATTRIBUTE_PROGRAMMATIC_EVENTviaLaunchConfig. - Mapping to the native launch attribute is tested.
Describe alternatives you've considered
Use cuda.bindings.driver (CUlaunchAttribute / CU_LAUNCH_ATTRIBUTE_PROGRAMMATIC_EVENT) and cuLaunchKernelEx directly.
Downside: leaves cuda.core users without a first-class LaunchConfig API; they must drop to low-level bindings, manage the attribute array themselves, and lose consistency with other LaunchConfig launch attributes (programmatic_stream_serialization, etc.).
Additional context
Incremental LaunchConfig attribute coverage under #496 (same approach as #1334 for programmatic_stream_serialization).
No example code in the design notes for this attribute.
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
launch_attrinLaunchConfigctor #496[-]Add support for CU_LAUNCH_ATTRIBUTE_PROGRAMMATIC_EVENT in LaunchConfig[/-][+][FEA]: Add support for CU_LAUNCH_ATTRIBUTE_PROGRAMMATIC_EVENT in LaunchConfig[/+][-][FEA]: Add support for CU_LAUNCH_ATTRIBUTE_PROGRAMMATIC_EVENT in LaunchConfig[/-][+][FEA]: Support CU_LAUNCH_ATTRIBUTE_PROGRAMMATIC_EVENT in LaunchConfig[/+]atiaomar1978-hub commentedon Sep 4, 2026
@lijinf2 — I'm working on #2629 / PR #2703 (
LaunchConfig.cluster_scheduling_policy_preference) and noticed this related item under #496.Would it be helpful if I picked up #2630 (
CU_LAUNCH_ATTRIBUTE_PROGRAMMATIC_EVENTonLaunchConfig)? It looks like the same incrementalLaunchConfigattribute pattern as #1334 and the cluster scheduling work, and I'd plan to follow the same approach: expose the attribute onLaunchConfig, wire it through native launch config conversion, and add tests for the mapping.Happy to wait until #2703 lands, or start in parallel if you prefer — just wanted to check with you first since you're assigned here. Thanks.
atiaomar1978-hub commentedon Sep 15, 2026
@lijinf2 — gentle reminder on my Sep 4 comment: I offered to pick up #2630 (
CU_LAUNCH_ATTRIBUTE_PROGRAMMATIC_EVENTonLaunchConfig) after #2629 / PR #2703 landed.That blocker is done — #2703 merged and #2629 closed. I'd follow the same pattern as the cluster scheduling work: expose the attribute on
LaunchConfig, wire it through native launch config conversion, and add mapping/validation tests.Would you like me to take #2630? Happy to wait for assignment or any design notes before opening a PR.
Thanks!