Skip to content

UCT/ROCM: adjust hsa memory type check for new rocm releases - v1.20.x - #11244

Merged
yosefe merged 1 commit into
openucx:v1.20.xfrom
mshanthagit:pr/hipMallocManaged-fix-cherry-pick
Mar 11, 2026
Merged

yosefe merged 1 commit into
openucx:v1.20.xfrom
mshanthagit:pr/hipMallocManaged-fix-cherry-pick

Conversation

@mshanthagit

Copy link
Copy Markdown
Contributor
  • UCT/ROCM: adjust hsa memory type check for new rocm releases

Newer rocm releases return HSA_EXT_POINTER_TYPE_RESERVED_ADDR instead of HSA_EXT_POINTER_TYPE_UNKNOWN for hip managed memory.

Add rocm version detection and guard code based on the detected version

  • UCT/ROCM: Fix formatting issue and update the Copyright date

  • UCT/ROCM: Addressing review comments

What?

Cherry-picking the commit from the master branch

Why?

Bug-fix being propagated from master to v1.20.x

How?

It is optional, but for complex PRs, please provide information about the design,
architecture, approach, etc.

…#11236)

* UCT/ROCM: adjust hsa memory type check for new rocm releases

Newer rocm releases return HSA_EXT_POINTER_TYPE_RESERVED_ADDR instead of
HSA_EXT_POINTER_TYPE_UNKNOWN for hip managed memory.

Add rocm version detection and guard code based on the detected version

* UCT/ROCM: Fix formatting issue and update the Copyright date

* UCT/ROCM: Addressing review comments
@mshanthagit
mshanthagit marked this pull request as ready for review March 10, 2026 05:27
@tvegas1 tvegas1 changed the title UCT/ROCM: adjust hsa memory type check for new rocm releases (#11236) UCT/ROCM: adjust hsa memory type check for new rocm releases - v1.20.x Mar 10, 2026
@mshanthagit

Copy link
Copy Markdown
Contributor Author

@tvegas1 can you please merge this PR so that it can be part of the next release (1.20.1?)?

@yosefe
yosefe merged commit e4932d0 into openucx:v1.20.x Mar 11, 2026
143 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants