You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(cuda.core): grant the current device access to PinnedMemoryResource pools - #3405
A host memory pool is accessible only from the host by default, so kernels faulted on PinnedMemoryResource buffers. The resource now grants the current device read/write access with cuMemPoolSetAccess, for both a created pool and the default host pool. Pools imported over IPC are not covered.
@Andy-Jost ready for review. It grants the current device read/write on both pool paths, as you described on #3205. The kernel test faults on main and passes with the fix, with and without numa_id. Could you /ok to test 036e4a0?
Kernels can now read from and write to pinned-memory buffers using the device that was active when the memory resource was created. This applies to resources using the driver’s current memory pool, as well as host and NUMA-specific pools.
Other devices do not receive access to these buffers automatically; access remains limited to the device active at creation.
PinnedMemoryResource now grants the device current at resource creation read/write access to supported host memory pools. Tests exercise kernel access for current, new, and NUMA pools. Documentation describes which device can access the buffers.
Changes: Pinned memory device access
Layer / File(s)
Summary
Grant current-device access during pool initialization cuda_core/cuda/core/_memory/_pinned_memory_resource.pyx
Initialization checks support for the relevant host pool type. When supported, it sets read/write access for the device current at creation.
Test and document device access cuda_core/cuda/core/_memory/_pinned_memory_resource.pyi, cuda_core/cuda/core/_memory/_pinned_memory_resource.pyx, cuda_core/tests/test_memory.py, cuda_core/docs/source/release/1.3.0-notes.rst
The test launches a kernel that reads and writes buffers from current, new, and NUMA pools. The documentation describes the access rule and the release notes describe the fix.
Assessment against linked issues
Objective
Addressed
Explanation
Test kernel reads and writes on the allocating device, with and without numa_id [#3205]
✅
If kernel access faults, grant current-device read/write access during pool creation and retain is_device_accessible as True [#3205]
✅
Possibly related issues
NVIDIA/cuda-python#2795: The PR uses host-pool capability checks to decide whether to grant access; the issue reports possible false negatives for supported NUMA pools.
NVIDIA/cuda-python#3219: The PR adds kernel-access coverage for NUMA-bound pinned-memory buffers.
Suggested reviewers:uday1o1
Change: Bug fix · Severity of issue fixed: Medium
Merge Risk: Low · up to 036e4
The pinned-memory fix works for newly created pools, but the docs promise more than the code delivers for imported pools and shared current pools. Correct the documentation before or soon after merge.
Security architecture risk: Low · up to 036e4
The change restores intended GPU access to pinned buffers. The main concern is that access granted to a shared pool can persist across resource lifetimes and accumulate across devices, so the documented exclusion of other devices is not a reliable isolation guarantee. No cross-process or privilege-escalation attack was demonstrated.
Retained concerns
Low · security · inferred: The documented exclusion of other devices does not hold as a general guarantee for shared pools. Creating resources under different devices against the same current/default pool can accumulate pool-wide read/write grants, and closing a resource does not revoke its grant. Applications must not treat resource creation or close as a per-device isolation boundary.
Security review details
Security Blast Radius
inferred — The authorization unit is the entire selected pool, not only buffers allocated through the new wrapper. On a reused current/default pool, the effective exposure includes other allocations in that pool for each device granted access.
Security Findings and Attack Paths
inferred — The supported concern requires application execution to create resources under multiple supported devices against the same pool. This is a misleading isolation contract, not a demonstrated unauthenticated or cross-tenant exploit. Host access predates the PR, and explicit IPC sharing remains a separate mechanism.
Trust Boundaries and Controls
observed — The grant uses the current CUDA device identity and is gated by host or host-NUMA capability. These are device-selection and compatibility controls, not tenant authorization or a per-resource device allowlist.
Resilience and Maintainability Implications
inferred — Owned-pool constructor failures are contained by the owning handle's automatic destruction when references are released. This counters a pool-leak concern after access configuration fails, but does not provide permission rollback for driver-managed shared pools.
Hardening Proposals
proposed — Define shared-pool access as cumulative pool policy rather than resource-local isolation. Where isolation is required, use a dedicated pool with explicit device permissions and ownership; do not automatically revoke shared permissions on wrapper close, since other users may depend on them.
- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Tip
🎯 Customize your risk assessments
Guide how CodeRabbit assesses merge risk and security architecture risk. Highlight sensitive changes and explain your security boundaries using Merge Risk Instructions and Security Risk Instructions in your review settings. Security architecture risk assessments require the Advanced plan or above.
✅ Automatic approvals, with your rules
Let CodeRabbit approve pull requests once required threads are resolved, pre-merge checks pass, and your risk limits are met. Enable Automatic approvals in review settings, with overrides for teams or file paths.
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review.
CUDA driver API cuMemGetMemPool host location current pool CU_MEM_LOCATION_TYPE_HOST cuMemPoolSetAccess other device access flags independent
Result:
Sources consulted:
- 6.39. Stream Ordered Memory Allocator — CUDA Driver API Reference Manual 13.5 documentation — https://docs.nvidia.com/cuda/cuda-driver-api/cuda_driver_api/group__CUDA__MALLOC__ASYNC.html
- 4.3. Stream-Ordered Memory Allocator — CUDA Programming Guide — https://docs.nvidia.com/cuda/cuda-programming-guide/04-special-topics/stream-ordered-memory-allocation.html
- CUDA Driver API — https://docs.nvidia.com/cuda/pdf/CUDA_Driver_API.pdf
- 6.5. Data types used by CUDA driver — CUDA Driver API Reference Manual 13.5 documentation — https://docs.nvidia.com/cuda/cuda-driver-api/cuda_driver_api/group__CUDA__TYPES.html
- …and 28 more
Script executed:
nl -ba cuda_core/cuda/core/_memory/_memory_pool.pyx | sed -n '400,435p'
nl -ba cuda_core/cuda/core/_memory/_location.pyx | sed -n '1,120p'
Repository: NVIDIA/cuda-python
Length of output: 1675
Web query:
CUDA 13 driver cuMemPoolSetAccess "specified" locations "access" map allocations does not affect other locations
Result:
Sources consulted:
- CUDA Driver API :: CUDA Toolkit Documentation — https://docs.nvidia.com/cuda/archive/13.0.0/cuda-driver-api/group__CUDA__MALLOC__ASYNC.html
- 6.39. Stream Ordered Memory Allocator — CUDA Driver API Reference Manual 13.5 documentation — https://docs.nvidia.com/cuda/cuda-driver-api/cuda_driver_api/group__CUDA__MALLOC__ASYNC.html
- 4.3. Stream-Ordered Memory Allocator — CUDA Programming Guide — https://docs.nvidia.com/cuda/archive/13.2.1/cuda-programming-guide/04-special-topics/stream-ordered-memory-allocation.html
- …and 17 more
Script executed:
rg -n -F 'cumemlocation_from_id' cuda_core/cuda/core/_memory/_location.pxd cuda_core/cuda/core/_memory
nl -ba cuda_core/cuda/core/_memory/_location.pxd | sed -n '1,110p'
nl -ba cuda_core/cuda/core/_memory/_peer_access_utils.pyx | sed -n '135,175p'
Repository: NVIDIA/cuda-python
Length of output: 7737
Web query:
site:docs.nvidia.com/cuda/archive/13.0.0/cuda-driver-api/group__CUDA__MALLOC__ASYNC.html "cuMemPoolSetAccess" "The access" "locations"
Result:
Sources consulted:
- CUDA Driver API :: CUDA Toolkit Documentation — https://docs.nvidia.com/cuda/archive/13.0.0/cuda-driver-api/group__CUDA__MALLOC__ASYNC.html
- CUDA Driver API :: CUDA Toolkit Documentation — https://docs.nvidia.com/cuda/archive/13.0.0/cuda-driver-api/group__CUDA__VA.html
- CUDA Driver API — https://docs.nvidia.com/cuda/archive/13.0.0/pdf/CUDA_Driver_API.pdf
- CUDA Driver API :: CUDA Toolkit Documentation — https://docs.nvidia.com/cuda/archive/13.0.2/cuda-driver-api/group__CUDA__MALLOC__ASYNC.html
- …and 19 more
important: Qualify the other-device access claim.
Two resources created without options can share the current pool. If they are created on different supported devices, both devices can retain access to all allocations in that pool. Qualify the claim here and in _pinned_memory_resource.pyi.
CUDA cuMemPoolCreate HOST_NUMA pool initially only accessible host cuMemPoolImportFromShareableHandle access imported host memory pool GPU access permissions
Result:
Sources consulted:
- 6.39. Stream Ordered Memory Allocator — CUDA Driver API Reference Manual 13.5 documentation — https://docs.nvidia.com/cuda/cuda-driver-api/cuda_driver_api/group__CUDA__MALLOC__ASYNC.html
- 6.38. Stream Ordered Memory Allocator — CUDA Driver API Reference Manual 13.4 documentation — https://docs.nvidia.com/cuda/archive/13.4.2/cuda-driver-api/cuda_driver_api/group__CUDA__MALLOC__ASYNC.html
- 4.3. Stream-Ordered Memory Allocator — CUDA Programming Guide — https://docs.nvidia.com/cuda/cuda-programming-guide/04-special-topics/stream-ordered-memory-allocation.html
- …and 19 more
important: Qualify the device-access claims for imported pools.
from_allocation_handle() does not grant device access, and imported pools do not inherit the exporter's access grants. A kernel that uses an imported allocation can fault.
Exclude imported pools from the guarantee in the property, class documentation, stub, and release notes.
…yResource (#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>
Andy-Jost
added a commit
to Andy-Jost/cuda-python
that referenced
this pull request
Nov 17, 2026
…yResource (NVIDIA#3475)
Since NVIDIA#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 NVIDIA#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.
ClosesNVIDIA#3451
Co-authored-by: Andy Jost <ajost@nvidia.com>
(cherry picked from commit d94f19c)
* [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>
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
cuda.coreEverything related to the cuda.core moduleenhancementAny code-related improvementsP2Low priority - Nice to have
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.
Description
closes #3205
A host memory pool is accessible only from the host by default, so kernels faulted on PinnedMemoryResource buffers. The resource now grants the current device read/write access with cuMemPoolSetAccess, for both a created pool and the default host pool. Pools imported over IPC are not covered.
Checklist