Allow host-pinned pointers in SetVals()

[cliffburdick]

No description provided.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[cliffburdick]

/build

[greptile-apps]

Greptile Summary

Extends SetVals() functionality to support host-accessible pointers (managed, host-pinned, or ATS-mapped) instead of only CUDA managed pointers. The implementation replaces IsManagedPointer() with IsHostAccessiblePointer(), which uses CU_POINTER_ATTRIBUTE_HOST_POINTER to determine if a pointer can be accessed from the host. All documentation comments and error messages have been updated to reflect the expanded support. The [[maybe_unused]] attribute has been properly applied to the retval variable as noted in previous review feedback.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The change is well-implemented and extends functionality in a backward-compatible way. The new IsHostAccessiblePointer() method correctly uses CUDA's pointer attribute API, maintains the [[maybe_unused]] attribute for release builds, and updates all relevant documentation. The logic properly checks for host-accessible pointers by verifying the returned host pointer is non-null.
• No files require special attention

Important Files Changed

Filename	Overview
include/matx/core/tensor.h	Extends SetVals() to support host-pinned and ATS-mapped pointers by replacing IsManagedPointer() with IsHostAccessiblePointer(), includes proper [[maybe_unused]] attribute

_{Last reviewed commit: 1994bbc}

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}