Repository navigation
Unify the async host runtime and remove cuda_async::simt - #1604
Conversation
DeviceBuffer::cast_elem, DeviceBuffer::cast_chunks, and Tensor::reinterpret reinterpreted device bytes as any element type of the right size and alignment, which let a u8 buffer become a DeviceBuffer<bool> or Tensor<bool> holding values other than 0 and 1 (NVIDIA#1506). The casts now require bytemuck::AnyBitPattern of their target, so bool is rejected at compile time, and bool implements DeviceCopy: a typed buffer holds valid values by construction, so bool buffers can be allocated, filled, launched, and read back like any other element type. cuda-core re-exports bytemuck, implements Pod for the DType newtypes, and enables half's bytemuck feature for f16 and bf16. The atomic wrappers in cuda-device are not Copy, so they cannot be AnyBitPattern. DeviceBuffer gains wrap_elem and peel_elem, bounded on bytemuck::TransparentWrapper, to view a scalar buffer as its atomic wrapper and back. cuda-device implements TransparentWrapper for its atomic types and Pod for its vector types, and the examples that cast into atomics use the new methods. Every example lock gains the bytemuck dependency of cuda-device. Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
…nd SIMT Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
d1ee216 to
f0f61e2
Compare
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
e97d214 to
fcfe932
Compare
…uncher Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
…eBuffers Signed-off-by: nihalpasham <nihalp@nvidia.com>
…viceBox::from_raw_parts and update docs Signed-off-by: nihalpasham <nihalp@nvidia.com>
|
Looks good! Pushed a small commit (
|
…ybitpattern-casts Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com> # Conflicts: # cutile-rs/CHANGELOG.md
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
|
/ok to test 3ae634e |
|
The updated combined host stack at The source changes and merge resolutions have been self-reviewed. The refreshed Draft #1613 is updated to |
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
|
/ok to test 95a51d7 |
…ries Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
…py (#1516) Closes #1506. First change under #1460; implements the `bool` decision recorded there and in #1461 and #1503. Safe element casts previously checked size and alignment but could turn a byte containing `2` into a Rust `bool`. This PR rejects those casts, supports initialized `bool` buffers, and closes the host-side initialization, atomic-reference, kernel-argument, and pinned-alignment holes found during review and follow-up auditing. ## Element validity `DeviceBuffer::cast_elem`, `cast_chunks`, `can_cast_chunks`, and `Tensor::reinterpret` require `bytemuck::AnyBitPattern` on the target. Casting into `bool` is therefore a compile error. The two safe buffer casts also require `T: bytemuck::NoUninit` on their source: padding or `MaybeUninit` bytes must not become initialized destination values. `can_cast_chunks` remains a layout query. These bounds do not restrict `DeviceCopy` itself, and bool-to-byte casts remain supported. `bool` implements `DeviceCopy`: valid values can be copied between host and device, and its all-zero representation is valid. `DeviceCopy` does not promise that every bit pattern is valid. It remains independent of `DType`. The numeric `DType` newtypes implement `Pod`, and `half` enables its bytemuck feature, preserving numeric reinterpretation targets. cuda-core re-exports `bytemuck` for downstream marker implementations. Vector types in cuda-device also implement `Pod`, preserving `cast_chunks` usage. ## Owned atomic-buffer conversions `wrap_elem` and `peel_elem` use the unsafe marker `DeviceRepr<Inner>`. Its contract requires identical layout, valid initialized representations in both directions, no element destruction, and no additional ownership obligations. It has no methods and grants no reference conversions. The integer and floating-point atomic macros implement `DeviceRepr`, not `TransparentWrapper`. Consequently, safe `DeviceAtomicU32::wrap_ref(&u32)` and the reverse `peel_ref` conversion are unavailable. Owned scalar buffers can still be wrapped for atomic kernel access and peeled for readback, retaining their allocation, context, and deallocation stream. Kernel accesses must obey the existing borrowing and synchronization contracts. The marker lives in the dependency-free, `no_std` cuda-repr crate and is re-exported by cuda-core and cuda-device. This lets both sides share one trait without making kernel-only crates depend on the host runtime. The dependent lockfiles add this local package without changing registry or git dependencies. CI path filters include the new crate. The atomic examples use `wrap_elem`/`peel_elem`. `KernelSliceArg` is not restricted to `DeviceCopy`, since atomic wrappers are legitimate kernel element types that cannot implement `Copy`. ## Completed zero-initialization `DeviceBuffer::zeroed` queues the zero-fill and synchronizes its stream before returning. A safe readback or launch on another stream can therefore rely on initialization having completed, including for `bool`. Empty allocations retain their fast path. This makes nonempty `zeroed` a blocking constructor. Asynchronous initialization with automatically retained completion dependencies belongs to the subsequent runtime work; callers are not asked to repair a safe API through manual synchronization. ## Host-side argument contracts and pinned alignment `KernelInputStored` and `KernelOutputStored` now require `unsafe impl`. Their contracts cover truthful dtype/layout/specialization metadata, argument ABI, addressable extent, and storage/access retention through completion and graph replay. Previously an entirely safe custom binding could present `Tensor<bool>` storage as `u8` output, so a normal byte kernel could write invalid bool values. The input counterpart could similarly mislabel arbitrary byte storage as booleans. The safe `KernelInput`/`KernelOutput` conversion traits remain available and must return stored bindings satisfying those contracts. Existing owned, borrowed, view, and mapped bindings retain their behavior. `PinnedHostBuffer` reserves alignment slack, exposes an aligned interior pointer, and retains the original CUDA pointer for deallocation. It also rejects allocation sizes that exceed Rust slice/pointer-arithmetic limits. Empty and zero-sized buffers keep their aligned dangling pointers and allocation-free behavior. ## Tensor alias accounting Tensor aliases and lazy copy operations share a separate ownership token. Completion leases retain the storage itself without contributing to that token. Uniqueness therefore stays correct while a lease is being registered or destroyed: a real alias cannot become a mutable partition, and retiring a lease cannot spuriously reject a unique tensor. Access exclusion and completion retention remain enforced. The acquisition and destruction regressions fail on the previous implementation and pass with this change. A separate test preserves ownership held by an unsubmitted copy operation. ## Compatibility and validation The new `AnyBitPattern` target and `NoUninit` source bounds are breaking changes for safe casts whose element types do not implement those traits. Numeric targets remain supported; atomics use the owned-buffer conversions. Tuple types remain usable as buffer elements but are not reinterpretation targets. Custom stored Tile argument implementations must now explicitly uphold the documented unsafe contract. Earlier validation of the underlying changes: - Full cuda-core and cuda-device tests, including GPU buffer tests, compile-fail tests for invalid bool casts and both atomic shared-reference conversions, and layout checks for all 21 scoped atomic types. - A gated-stream regression that fails without the initialization synchronization and passes with it. It inspects bytes, avoiding invalid Rust bool values in the failing case. - Owned wrapper roundtrip coverage for pointer identity, context, stream retention, and readback. - GPU runs of `legacy_atomic_rmw_cas`, `legacy_atomic_fadd`, and `hashmap` on an RTX 5090; all six Tile tensor reinterpretation tests. - Clippy for cuda-core/cuda-repr, cuda-device/cuda-host, and cutile; host and component formatting; cuda-core/cuda-repr rustdoc with warnings denied. - Device-only build, example lock consistency, dependency-license/SPDX/source-reference/test-matrix guards, and cargo-deny for the host, SIMT, backend, device-only, and Tile workspaces. The Tile UI snapshot now uses the normalized external-crate path. Both UI harness tests (all 12 compile-fail cases) pass, and the CPU CI script now runs them. The version-only update to the planned v0.5.0 API boundary has landed on main in #1614; host and Tile semver checks pass. SIMT workflow branch filters now include stacked PRs targeting `pull-request/<n>` prerequisite mirrors. Follow-up validation for the host-side argument and pinned-buffer fixes: - Both new compile-fail cases compiled before the fix and now fail specifically because `unsafe impl` is required; snapshots were reviewed and rerun without overwrite. - The pinned alignment regression failed before the fix, without constructing misaligned references. It now passes, alongside over-aligned copying, empty/ZST coverage, and allocation-size boundary tests. - Full cuda-core suite: 105 passed, 3 ignored. Selected Tile library/GPU/tensor/view suites: 168 passed, 2 ignored. Submission-lifetime suite: all 9 passed, including forgotten borrowed work and graph replay. - cuda-core and cutile Clippy with warnings denied, host/Tile formatting, and SPDX checks passed. cuda-core rustdoc with warnings denied passed. Tile documentation builds, but its stricter warnings-as-errors check reports 12 existing link warnings outside the added trait documentation. Earlier host-argument follow-up validation: the complete CPU runner passes (1,408 tests, 98 intentionally ignored), including the Tile UI suites. All 25 targeted GPU buffer and pinned-host-buffer tests pass, including the cross-stream initialization regression. The branch includes the #1602 debug-source fixes and the same version metadata as #1614. Current validation (2026-10-30): head `117205c1277a9e6d422df20499342690b412bc16` includes main through `76ac10216`. The new regression fixture compiled before the source-validity fix, then all five trybuild cases passed afterward without snapshot regeneration. The new-main `math_special` example lockfile includes the host dependencies at the versions used by other examples; the full example dependency-policy guard passes. Fresh CI is running. GitHub dismissed the previous approval after the source changes, and renewed review has been requested. The expanded atomics example from current main uses owned `wrap_elem`/`peel_elem` conversions, with explicit checked ownership transfer for its standard-library atomic case. Strict example Clippy passes, and all 24 runtime atomic cases pass on both this PR and the combined shared-host stack on RTX 5090 / CUDA 13.3. Merge-readiness refresh (2026-10-30): head `c5ea583c5b5f06b424a9ab0c48174c771e99ff52` includes main through the merged #1480 (`b025a8b31`). The only manual conflict resolution preserved both changelog entries; source and tests from #1480 merged unchanged. The combined release candidate has an identical source/test tree to previously validated `c6c5a860a` (only the changelog and merge ancestry changed). New-head CI is running. Merge #1516 into main first, then retarget #1603 to main and merge it, then retarget #1604 to main and merge it. Do not merge the children into the temporary `pull-request/*` bases. Issue/release inclusion tracking: #1606. --------- Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com> Co-authored-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
…tree Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
…nd SIMT (#1603) Tile and SIMT currently expose separate `cuda-core` contexts, streams, launch configurations, and allocation owners. A buffer moving between the models consequently needs raw-pointer adaptation, and the separate runtimes cannot coordinate lifetime or conflicting accesses. This removes `cuda_core::simt` and gives both models the same host handles and allocation owner. `Device` identifies a physical GPU; `Context` owns or borrows the actual CUDA context. Typed buffers, contiguous sliced views, foreign owners, and Tile tensors share allocation identity and access tracking. `Tensor::from_buffer`, `into_buffer`, and `as_buffer` transfer or borrow storage without copying device memory. Ownership transfer rejects live typed aliases, preserving the boolean representation guarantees in #1516. Safe submissions retain allocations and access leases until GPU completion, including after a borrowed launch future is dropped or forgotten. Shared references to device atomics are conservatively tracked as writable. Buffer and stream destructors retire work without waiting on the dropping thread; unknown completion retains resources instead of freeing active memory. The existing SIMT async launcher receives the small retention bridge needed to make this core migration safe before its separate consolidation. Allocation uniqueness counts user-visible byte views independently of completion leases. This removes the retirement window where a decremented lease count still had a live Arc and made a unique buffer appear aliased. The same separation at the Tensor layer comes from #1516; both checks remain required for zero-copy ownership transfer. Nihal's fixes preserve ordinary shared-read permissions on empty and peeled buffers and wait for retirement before checking reclaimed VRAM. Consumer code, generated launchers, examples, templates, documentation, tests, and CI paths use the shared API. Tile numeric storage wrappers also implement `DeviceCopy`; `DType` and `DeviceCopy` remain independent traits. Stack: #1516 merged into `main` as `dfea11698aa63b9a42d9f8181a711d27774d0722`. This PR now targets `main` and contains only the core migration. Merge this before the follow-up #1604, which removes `cuda_async::simt`. Validation: - Full `cuda-core` suite: 111 passed; full `cuda-async` suite: 151 passed. - Selected Tile library/GPU/interop/submission-lifetime suites: 156 passed, including graph replay, offset preservation, alias rejection, and forgotten futures. - SIMT host/macro suites: 261 passed; cargo-oxide: 268 passed. Three additional GPU launch-lifetime regressions pass explicitly with `--ignored`. - Clippy with warnings denied for host workspace, Tile, and affected SIMT packages; strict cuda-core rustdoc; formatting, host-path and SPDX guards. The Tile workspace is also checked with every example feature enabled, including Candle CPU references. - Dependency checks pass for the host, SIMT, backend, device-only fixture, and Tile workspaces. GPU validation used a single RTX 5090. Multi-GPU/NVLink cases self-skip on this machine; this does not claim multi-GPU coverage. Existing deliberately ignored tests remain ignored. Closes #1460. Closes #1504. The global-context re-entry/state-machine follow-up remains tracked separately in #1403. Earlier follow-up validation: all 50 cuda-core unit tests and all nine targeted shared-allocation/retirement GPU tests pass, as does cuda-core Clippy with warnings denied. The new concurrency regression failed 3,308 uniqueness checks on the previous implementation and passes with the fix. Earlier main integration: Merged the updated #1516 prerequisite and migrated the new CuTe host consumers to shared LaunchConfig and the explicit event-flags API. Affected-package Clippy and all 16 CuTe example/model workspace Clippy checks pass. CI passed before this refresh; current-head CI is tracked below. Current update (2026-10-30), head `98d0820debc6f3994cb45c041ac182e174bff364`: Plain completion leases now retain allocation access independently of user-view tokens, so tensor-to-buffer conversion preserves unique ownership without weakening cross-stream exclusion or recorded graph ownership. The combined stack passes 1,427 CPU/assembler tests, 750 GPU tests, 27 supported examples and eight benchmark smoke tests. Initial disk exhaustion was resolved and the affected suites rerun successfully. The expanded atomic example is migrated to owned conversions; all 24 atomic GPU cases also pass on the final shared-runtime head. Fresh CI is running; #1516 still needs renewed approval before this stack can merge into main. Merge status (2026-10-30): current head `ba76442278ad1d6c67070ef5fde3dd63efcddb85` records the accepted #1516 squash merge. The squash-merge tree exactly matches the accepted #1516 head; the ancestry-only refresh leaves this PR's entire file tree unchanged from its reviewed predecessor. After copy-pr-bot deleted the old temporary bases and automatically closed the stacked PRs, they were reopened against `main`; temporary restoration refs were removed. Merge order is #1603 then #1604. Fresh CI is running, and retargeting caused GitHub to require review again. Issue/release tracking: #1606. --------- Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com> Signed-off-by: nihalpasham <nihalp@nvidia.com> Co-authored-by: Melih Elibol <1884921+elibol@users.noreply.github.com> Co-authored-by: nihalpasham <nihalp@nvidia.com>
…d async tree Signed-off-by: Melih Elibol <1884921+elibol@users.noreply.github.com>
Tile operations and SIMT launches currently use separate async runtimes and cannot compose through the same operation types. This change removes
cuda_async::simtand routes both programming models through the sharedDeviceOp,DeviceFuture, execution context, scheduler, errors and launch API.Closes #1461. Prerequisite #1603 is merged into
mainas6a6372e4cc2e0f142471cf18f13b9072abe87757. This PR targetsmainand its diff now contains only the async migration. The development branch remains on the contributor's fork.KernelArgumentblanket implementation usesDeviceCopy. Generic Tile scalars requireDType + DeviceCopy; tensor-only type parameters retain their independentDTypecontract. The shared argument arena preserves inline storage, padded values, over-alignment and typed destruction for the explicit unsafe boxed-argument escape hatch.AsyncKernelLaunchBuilderrequires unsafe finalization before becoming a schedulable, immutable launch. Generated typed launchers retain their checked boundaries. Tile PDL and SIMT cluster/cooperative launch paths are preserved. Raw async macros marshal slice pointers and lengths as direct scalar values; optional CPU-reference examples use the corresponding scalar bounds.DeviceBoxtransfers to/from shared typed buffers without copying and preserves ordinary read permissions. ExistingDeviceOperation,and_then,applyandarcspellings delegate to the shared implementations.cutile_inter_kernelnow uses the normal shared launch API to update the Tile-produced allocation in place, checks its pointer and allocation identity, and verifies results. Consumers, generated-project templates, documentation, UI fixtures and GPU test entry points are migrated.AGENTS.mdrecords that future branches must originate from the user's fork.Validation: shared async tests and doctests; Tile unit, aggregate GPU, submission-lifetime, interop and UI tests; cuda-host/cuda-macros suites; 268 cargo-oxide tests; four explicit SIMT lifetime/concurrency GPU tests. Both
cargo oxide run cutile_inter_kernelandcargo oxide run async_mlppass. Miri passes all seven argument-storage tests, and Loom passes the completion-handoff model. Host/Tile/affected SIMT clippy checks, formatting, strict async rustdoc, SPDX/API-path guards and Tile dependency checks pass.GPU execution was validated on one RTX 5090. This does not add multi-GPU/NVLink hardware coverage. API migration and custom-operation retention obligations are documented in
cuda-async/README.md.Additional validation: the full CPU runner passes (1,381 tests; 94 intentionally ignored), all top-level SIMT example workspaces pass Clippy with warnings denied, and all 144 macro unit tests pass. The
host_closureGPU example also passes all 13 scenarios, covering the corrected async slice argument marshalling.Earlier follow-up validation after incorporating the updated #1516/#1603 stack: all 1,394 CPU tests pass (95 intentionally ignored), as do 138 selected Tile GPU/interop/graph/view/lifetime tests and all four explicit SIMT lifetime/concurrency tests. The original stress reproducer reports no false negatives in 1,000,000 raw-buffer uniqueness checks and no false positives in 100,000 aliased-tensor partition attempts. Nihal's
DeviceBox::from_raw_partsshared-read fix remains included.Restored the original cutile-rs
unsafe async_on()contract: the caller independently keeps all submitted resources alive and orders their accesses. On return, including an error,async_on()releases runtime owners and access leases without synchronization or background retention. Safe futures retain their nonblocking completion-based cleanup. The existing four-tensor launch benchmark now measures 1.88 µs/launch, down from 4.95 µs before this fix (earlier main baseline: 1.68 µs). No batching or new launch API is needed for this fix.Earlier main integration: Merged the updated #1603 prerequisite, including the CuTe host-consumer migration. The cuda-host, cuda-macros, ctm-rs and cute-rs suites pass (497 tests, 43 intentionally ignored), together with affected-package Clippy and all 16 CuTe example/model workspace Clippy checks. CI passed before this refresh; current-head CI is tracked below.
Validation for
b811b7067: all 133 cuda-async tests pass (14 intentionally ignored), all 11 Tile submission-lifetime tests and all four SIMT lifetime/concurrency GPU tests pass, and Clippy/formatting/rustdoc checks pass. Both new gated-stream regressions fail on the preceding code and pass here. That revision was validated before the current refresh.Current update (2026-10-30), head
95a51d708cc1dd203a922a28624aa087cb7a2176: Carries the #1516 source-validity and #1603 completion-retention fixes while preserving the reviewed async launch lifetime/access contracts. The combined stack passes 1,427 CPU/assembler tests, 750 GPU tests, 27 supported examples and eight benchmark smoke tests. Initial disk exhaustion was resolved and the affected suites rerun successfully. The expanded atomic example is migrated to owned conversions; all 24 atomic GPU cases also pass on the final shared-runtime head. Fresh CI is running; #1516 still needs renewed approval before this stack can merge into main.Merge status (2026-10-30): current head
21bc9bb783429ef39da7ee9ac63bbd686a3a5895records accepted #1603 squash ancestry. The squash commit's entire tree exactly matches the prerequisite head already included here (ba7644227). The apparent conflicts were duplicate history; this merge changes zero files relative to previously greenede42672a. GitHub reports the PR mergeable. Current-head CI has restarted; the previous identical tree passed all 70 applicable checks, including GPU tests (one expected skip). No test assertions were relaxed. The earlier intermittent drop-timing failure remains tracked as test-hardening follow-up #1680. Issue/release tracking: #1606.