Repository navigation
UCM: Propagate memory attributes in allocation events - #11646
Merged
Merged
Conversation
Contributor
Author
rakhmets
reviewed
Jul 14, 2026
rakhmets
approved these changes
Jul 14, 2026
Contributor
Author
|
@brminich / @tomerg-nvidia asap plz |
tomerg-nvidia
approved these changes
Jul 14, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What?
Propagate
sys_devandmem_flagsin UCM memory events and removeUCS_MEM_FLAG_NEEDS_QUERY.Why?
Device symbols require additional memory-attribute detection. Carrying attributes in the event avoids a synthetic query flag.
Fixes internal issue.
How?
Device-symbol events use CUDA-managed type, unknown sys_dev, and zero flags; other allocations are marked registerable.