Update on the newly added API hipblaslt-ext::isSolutionSupported()#8746
Merged
Conversation
Update on the newly added API hipblaslt-ext::isSolutionSupported()
randyh62
reviewed
Jun 24, 2026
randyh62
approved these changes
Jun 24, 2026
Co-authored-by: randyh62 <42045079+randyh62@users.noreply.github.com>
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.
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