Skip to content

[doc-only] docs(cuda.core): fix the floor-move wording; advise against pinning cuda-bindings - #3441

Merged
Andy-Jost merged 2 commits into
NVIDIA:mainfrom
Andy-Jost:ajost/support-floor-moves-sentence
Nov 10, 2026
Merged

Andy-Jost merged 2 commits into
NVIDIA:mainfrom
Andy-Jost:ajost/support-floor-moves-sentence

Conversation

@Andy-Jost

@Andy-Jost Andy-Jost commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Two small floor-policy doc fixes after the 1.3.0 release review.

  • support.rst, cuda_core/AGENTS.md, and .github/RELEASE-core.md said that the release notes list every floor move under "Breaking Changes". After review of [doc-only] docs(cuda.core): finalize 1.3.0 release notes, docs switcher, and metapackage pin #3424, the 1.3.0 notes list the floor move under Highlights and have no Breaking Changes section. The three files now say only that the release notes list every move.
  • install.rst now advises users not to pin cuda-bindings themselves. They depend on cuda-core with the cu12 or cu13 extra (or on the conda-forge package) and let cuda-core choose the cuda-bindings version, so a pin of their own does not conflict with the floor of a later release.

Follow-up to #3424 and #3425.

🤖 Generated with Claude Code

…r policy

The release notes no longer have a Breaking Changes section for a floor
move; 1.3.0 lists it under Highlights. Say only that the release notes
list every move.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Andy-Jost Andy-Jost added this to the cuda.core next milestone Nov 10, 2026
@Andy-Jost Andy-Jost added documentation Improvements or additions to documentation P0 High priority - Must do! cuda.core Everything related to the cuda.core module labels Nov 10, 2026
@Andy-Jost Andy-Jost self-assigned this Nov 10, 2026
@github-actions github-actions Bot added the CI/CD CI/CD infrastructure label Nov 10, 2026
@coderabbitai

coderabbitai Bot commented Nov 10, 2026 •

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

  • Documentation
    • Updated release-note guidance to include each bindings minimum-version change and the new minimum version, without requiring a “Breaking Changes” entry.
    • Updated PyPI and Conda installation guidance to recommend selecting the appropriate CUDA extra on PyPI and letting cuda-core choose a compatible cuda-bindings version, rather than pinning it.

Release and support guidance changes how bindings-floor moves are described in release notes. Installation guidance for PyPI and Conda advises users not to pin cuda-bindings and to let cuda-core select a compatible version.

Changes: Bindings-floor guidance

Layer / File(s) Summary
Update floor-move release-note guidance
cuda_core/AGENTS.md, .github/RELEASE-core.md, cuda_core/docs/source/support.rst
The guidance asks release notes to identify new floors without requiring placement under “Breaking Changes.”
Document cuda-bindings selection
cuda_core/docs/source/install.rst
The PyPI and Conda instructions advise users not to pin cuda-bindings and to let cuda-core choose its version.

Possibly related issues

Suggested reviewers: rwgk

Change: Other

Merge Risk: Minimal · up to 818a6

The updated release and installation guidance is mergeable after normal checks. Compatibility of a future Conda package remains a separate release-time verification.

Architecture risk: Low · up to 818a6

The change affects 1 system.

Changed systems: cuda_core

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

  • observed — cuda_core (service) was modified; 3 changed files map to changed impact.

Before / after behavior

  • observed — Modified behavior in cuda_core/AGENTS.md: The release-notes instruction now asks for an entry naming the new floors, replacing the requirement to label it “Breaking Changes.”
  • observed — Modified behavior in cuda_core/docs/source/support.rst: The sentence about floor moves no longer specifies that release notes list them under “Breaking Changes.”
  • observed — Modified behavior in cuda_core/docs/source/install.rst: The PyPI instructions add guidance not to pin cuda-bindings; users should select the cu12 or cu13 extra and let cuda-core choose its version, since a user pin can conflict with a later release’s floor.
  • observed — Modified behavior in cuda_core/docs/source/install.rst: The Conda instructions now advise against pinning cuda-bindings and say to let cuda-core choose its version.
- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Recent review info

Run configuration

Commits

Reviewing files that changed from the base of the PR and between 97d77db and 818a62f.

Files selected for processing: 1

  • cuda_core/docs/source/install.rst

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 10 remain after this review.

@mdboom mdboom 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.

Good improvement, given the sensitivity of the phrase "Breaking Changes".

Users who pin cuda-bindings themselves can conflict with the floor of a
later cuda-core release. Tell them to depend on cuda-core with the cu12
or cu13 extra and let cuda-core choose the cuda-bindings version.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Andy-Jost Andy-Jost changed the title [doc-only] docs(cuda.core): drop the Breaking Changes section name from the floor policy [doc-only] docs(cuda.core): fix the floor-move wording; advise against pinning cuda-bindings Nov 10, 2026
@Andy-Jost
Andy-Jost requested review from leofang and rwgk November 10, 2026 22:43
@github-actions

github-actions Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor
Doc Preview CI
Preview removed because the pull request was closed or merged.

@Andy-Jost
Andy-Jost merged commit 83a3422 into NVIDIA:main Nov 10, 2026
36 checks passed
@Andy-Jost
Andy-Jost deleted the ajost/support-floor-moves-sentence branch November 10, 2026 23:07
github-actions Bot pushed a commit that referenced this pull request Nov 11, 2026
Removed preview folders for the following PRs:
- PR #3358
- PR #3410
- PR #3418
- PR #3424
- PR #3425
- PR #3431
- PR #3435
- PR #3437
- PR #3441
Andy-Jost added a commit that referenced this pull request Nov 18, 2026
* [doc-only] docs(cuda.core): fix the floor-move wording; advise against pinning cuda-bindings (#3441)

* docs(cuda.core): drop the Breaking Changes section name from the floor policy

The release notes no longer have a Breaking Changes section for a floor
move; 1.3.0 lists it under Highlights. Say only that the release notes
list every move.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(cuda.core): advise against pinning cuda-bindings next to cuda-core

Users who pin cuda-bindings themselves can conflict with the floor of a
later cuda-core release. Tell them to depend on cuda-core with the cu12
or cu13 extra and let cuda-core choose the cuda-bindings version.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 83a3422)

* Mark cuda-gdb source-line test thread_unsafe (#3433)

Signed-off-by: Ralf Juengling <rjuengling@nvidia.com>
(cherry picked from commit 1a22eec)

* fix(cuda.core): serialize pinned-memory kernel-access test on Windows (#3436)

* fix(cuda.core): serialize pinned-memory kernel-access test on Windows

closes #3426

Add @thread_unsafe_on_windows to the pinned-memory kernel-access test.
The test accesses host memory while parallel workers may execute GPU
work; synchronizing its own stream does not coordinate those workers.

This follows the guard used by similar tests on Windows and WSL.
Windows CI is needed to confirm it resolves the reported crashes.
The separate OOM failures remain under investigation.

Validation: Ruff and git diff --check pass.

* fix(cuda.core): report CUDA synchronization errors during test teardown

Check the cuCtxSynchronize result in init_cuda so asynchronous errors
surface during the triggering test's teardown instead of going unnoticed
until a later test. Always attempt context cleanup via finally.

Related to #3426.

* fix(cuda.core): synchronize the bound context during test teardown

Use device.sync() because the test wrapper may pop the current context
before init_cuda teardown. This avoids spurious INVALID_CONTEXT errors
while preserving synchronization error reporting and context cleanup.

Add regression coverage for a missing current context and cleanup after
synchronization failures.

Related to #3426.

* fix(cuda.core): serialize memory-pool watermark reset tests

Mark test_mempool_watermark_reset thread_unsafe, matching test_mempool_trim.
Both exercise the pool teardown and synchronization sequence associated
with the suspected driver race in #3350.

* fix(cuda.core): bypass access revocation when destroying host pools

Skip peer-access revocation for locally created HOST and HOST_NUMA pools
to investigate pinned-pool teardown OOMs and crashes. Continue destroying
the pools and preserve cleanup for device, managed, and imported pools.

This is a diagnostic workaround pending Windows CI validation.

Related to #3426.

* fix(cuda.core): preserve the first exception during fixture cleanup

Keep setup or synchronization failures primary and attach subsequent
cleanup failures as exception notes. Always attempt to pop the context.

Add regression coverage for combined failures, including interrupts.

* fix(cuda.core): limit host-pool cleanup workaround to pinned allocations

HOST and HOST_NUMA also describe managed-pool preferences. Check the allocation type so the pinned-memory workaround preserves managed-pool peer-access revocation.

Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>

* test(cuda.core): expose pinned allocation OOM and retain its traceback

Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>

* ci: diagnose PR3436 pinned pool teardown on Windows

Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>

* ci: move watermark investigation out of PR3436

Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>

* test(cuda.core): restore expected pinned allocation OOM handling

Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>

* revert(cuda.core): defer pinned host pool cleanup workaround

Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>

---------

Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
Co-authored-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
(cherry picked from commit b715078)

* [no-ci] ci: exclude unavailable historical GitHub references (#3471)

* ci: exclude unavailable historical GitHub references

Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>

* ci: require manual copy-pr-bot approval

Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>

---------

Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
(cherry picked from commit 3991a69)

* cuda.core: map ml_dtypes bfloat16 to kDLBfloat in DLPack export (#3359)

_smv_dtype_numpy_to_dlpack dispatched on numpy dtype kind, but
ml_dtypes.bfloat16 has kind "V", so bf16 views fell through to the
unsupported-dtype BufferError and could not be re-exported, even though
the DLPack import path already accepts kDLBfloat and _tensor_map.pyx
maps bfloat16. Detect bfloat16 up front and export it as kDLBfloat
(16 bits).

The new round-trip test goes through StridedMemoryView.from_dlpack so
it cannot skip on stacks where NumPy's own DLPack support for extended
dtypes is unavailable, unlike the existing parametrized round-trip
test's NumPy-consumer probe.

Signed-off-by: Sainath-Reddy7 <180950590+Sainath-Reddy7@users.noreply.github.com>
Co-authored-by: Sainath-Reddy7 <180950590+Sainath-Reddy7@users.noreply.github.com>
Co-authored-by: Sebastian Berg <sebastianb@nvidia.com>
(cherry picked from commit d1d1457)

* fix(cuda.core): make IPC imports wait for a pending release of the same descriptor (#3450)

* fix(cuda.core): make IPC imports wait for a pending release of the same descriptor

deviceptr_import_ipc() shares one handle per descriptor because the
driver's first free of an imported pointer unmaps every import of it
(nvbug 5570902). The handle's deleter took ipc_import_mutex only after
the last reference was gone. In that gap an import found the cache entry
expired, re-imported the still-mapped pointer and registered a new entry.
The deleter then erased that new entry and freed the pointer, which
unmapped it under the new Buffer.

The cache entry now outlives the last reference and only its own deleter
erases it, under the mutex, together with the free. An import that finds
an expired entry waits on a condition variable until that release is
done, then imports fresh.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Use CTAD for the ipc_import_mutex locks

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 2f1185e)

* test(cuda.core): skip HOST graph allocation before CUDA 13 (#3446)

(cherry picked from commit 11cc666)

* test(cuda.core): query green stream contexts with v2 (#3448)

Signed-off-by: Rui Luo <ruluo@nvidia.com>
(cherry picked from commit 7076a67)

* test(cuda.core): skip the VMM RDMA policy test on WSL (#3478)

GPUDirect RDMA is not supported on WSL, but some drivers report the
capability there, and the RDMA-enabled VMM allocation in
test_vmm_allocator_policy_configuration then fails. Skip the test on
WSL; the capability checks stay as they are.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 36bc530)

* docs(cuda.core): add 1.3.0 release note for the IPC import/release race fix (#3479)

* docs(cuda.core): add 1.3.0 release note for the IPC import/release race fix

Follow-up to #3450, which merged without a release note.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(cuda.core): scope the IPC race release note to memory pool buffers

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit de4c60d)

* Fix conditional graph lifetime tests to use supported nodes (#3469)

* Fix conditional graph lifetime tests to use supported nodes

Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>

* ci: require manual copy-pr-bot approval

Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>

---------

Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
Co-authored-by: Andy Jost <ajost@nvidia.com>
(cherry picked from commit b80866b)

* fix(cuda.core): run cuMemPoolSetAccess in relaxed mode in PinnedMemoryResource (#3475)

Since #3405, PinnedMemoryResource.__init__ without options calls
cuMemPoolSetAccess to grant the current device read/write access to
the driver's default pool.  The driver refuses that call, and
invalidates the capture, while a global-mode capture is active on any
thread.  Users of PyTorch's torch.cuda.graph (which defaults to global
mode) therefore see CUDA_ERROR_STREAM_CAPTURE_UNSUPPORTED on
construction and CUDA_ERROR_STREAM_CAPTURE_INVALIDATED on end_building.

Fix: introduce MP_set_access in _memory_pool.pyx, wrapping
cuMemPoolSetAccess in the existing _enter_relaxed_capture_mode /
_exit_relaxed_capture_mode helpers, following the identical pattern
used by pool attribute reads and writes and trim() since #2834.
Call it from _PMR_init instead of the bare with-nogil block.

The with-options path (cuMemPoolCreate) is unaffected; that call is
still refused under global capture as documented in the 1.3.0 notes.

Add tests for the three capture combinations (global+same_thread,
global+other_thread, thread_local+same_thread) and a capture-mode
restore check modelled on test_dmr_init_restores_capture_mode.

Closes #3451

Co-authored-by: Andy Jost <ajost@nvidia.com>
(cherry picked from commit d94f19c)

* cuda.core: carry the cuda-bindings floors through minimal-sysctk12/13 extras (#3460)

* cuda.core: carry the cuda-bindings floors through minimal-sysctk extras

The floors lived only in the cu12/cu13 extras, so a package that depends
on plain cuda-core never passed them to pip or uv, and an older
cuda-bindings failed only at import (#3459).

Declare the floors in new minimal-sysctk12/13 extras, include them from
cu12/cu13, and depend on cuda-bindings without a version. The floor
parser, the CI wheel-floor reader, the pre-commit hook and the docs read
the new extras.

* cuda.core: read cu<N> floors through the minimal-sysctk self-reference

Drop the unversioned cuda-bindings from the base dependencies, so a
plain cuda-core install keeps asking for an extra.

Keep the floor readers on the cu<N> extras, as before, and teach them
to follow a cuda-core[...] self-reference and to skip an unversioned
cuda-bindings[all]. The cu<N> layout then yields the floor written in
minimal-sysctk<N>, and the existing tests of the cu<N> form stay as
they are. New tests cover the self-reference.

---------

Co-authored-by: Andy Jost <ajost@nvidia.com>
(cherry picked from commit ad38141)

---------

Signed-off-by: Ralf Juengling <rjuengling@nvidia.com>
Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
Signed-off-by: Sainath-Reddy7 <180950590+Sainath-Reddy7@users.noreply.github.com>
Signed-off-by: Rui Luo <ruluo@nvidia.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Ralf Juengling <rjuengling@nvidia.com>
Co-authored-by: jpascucci-nv <jpascucci@nvidia.com>
Co-authored-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
Co-authored-by: Ralf W. Grosse-Kunstleve <rwgkio@gmail.com>
Co-authored-by: B Sainath Reddy <bsainathreddy4@gmail.com>
Co-authored-by: Sainath-Reddy7 <180950590+Sainath-Reddy7@users.noreply.github.com>
Co-authored-by: Sebastian Berg <sebastianb@nvidia.com>
Co-authored-by: Rob Parolin <rparolin@users.noreply.github.com>
Co-authored-by: Rui Luo <ruluo@nvidia.com>
Co-authored-by: Leo Fang <leof@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI/CD CI/CD infrastructure cuda.core Everything related to the cuda.core module documentation Improvements or additions to documentation P0 High priority - Must do!

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants