Warn when ManagedMemoryResource is created without concurrent managed access #1618
+127
−2
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.
Summary
UserWarningwhenManagedMemoryResourceis created on a platform whereDevice.properties.concurrent_managed_accessis False. On such platforms, unsynchronized host access to managed memory causes a segfault.test_build_hooks.pywhensetuptoolsis unavailable (Python 3.14+).Closes #1607
Changes
cuda/core/_memory/_managed_memory_resource.pyx: Add_check_concurrent_managed_accesshelper with double-checked locking (warn-once pattern), andreset_concurrent_access_warning()for testing.tests/test_managed_memory_warning.py: New test file verifying the warning fires and only fires once.tests/test_build_hooks.py: Addpytest.importorskip("setuptools").Test Coverage
test_warning_emitted: Verifies the warning content (category, message text).test_warning_emitted_only_once: Verifies warn-once behavior across multiple resource creations.concurrent_managed_access=False).Made with Cursor