Skip to content

Update on the newly added API hipblaslt-ext::isSolutionSupported()#8746

Merged
mpanoop merged 2 commits into
ROCm:developfrom
mpanoop:develop
Jun 24, 2026
Merged

Update on the newly added API hipblaslt-ext::isSolutionSupported()#8746
mpanoop merged 2 commits into
ROCm:developfrom
mpanoop:develop

Conversation

@mpanoop

@mpanoop mpanoop commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Motivation

The PR #8082 introduces a new hipBLASLt integration from rocBLAS. Previous hipBLASLt integration for non-batched, strided-batched and general batched GEMMs was routed via hipblaslt-ext APIs. This was because hipBLASLt didn't support for General Batched GEMM and rocBLAS was routing the General Batched GEMM APIs to Grouped GEMM APIs which was exposed via hipblaslt-ext. Now that General Batched GEMM is supported in hipBLASLt, the hipBLASLt integration in rocBLAS can be streamlined to look similar to any other customer code which directly consumes hipBLASLt APIs.

Technical Details

There are still some rocBLAS specific scenarios like given a solution index in hipBLASLt Solution Library, validate if this solution is supported for a given GPU and problem type were the hipBLASLt APIs currently exposed won't suffice. Going via the hipblasLtMatmulAlgoGetHeuristics() API will mean we have to use the hipblasLtMatmulHeuristicResult_t parameter to pass the solution-index as input. But as per the API contract, this parameter is strictly output parameter. That's why we decided to expose an extension API which can directly route this to equivalent rocblaslt layer API.

Test Plan

rocBLAS tests in PR 8082 were using this new API for the scenarios where the solution-index were explicitly passed in.

Test Result

All tests are passing.

Submission Checklist

Update on the newly added API hipblaslt-ext::isSolutionSupported()
Comment thread projects/hipblaslt/CHANGELOG.md Outdated
Co-authored-by: randyh62 <42045079+randyh62@users.noreply.github.com>
@mpanoop mpanoop merged commit 4832985 into ROCm:develop Jun 24, 2026
29 of 32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants