-
-
Notifications
You must be signed in to change notification settings - Fork 11.7k
[AMD][ROCm]Quantization methods on ROCm; Fix _scaled_mm call #8380
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
simon-mo
merged 8 commits into
vllm-project:main
from
ROCm:rocm_quantization_enablement
Sep 18, 2024
Merged
Changes from 5 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
91e47ae
Enabling compressed-tensors and fbgemm quantization on rocm. Fixing s…
gshtras a108f1d
Update run-amd-test.sh - enable tests/kernels/test_fp8_quant.py
Alexei-V-Ivanov-AMD 36bce81
Merge remote-tracking branch 'origin/main' into rocm_quantization_ena…
gshtras 457c026
Restore blocking of the kernels/test_int8_quant.py test
Alexei-V-Ivanov-AMD 02074f4
Update vllm/config.py
gshtras ea368b0
Adapt the alternative scaled_mm call to torch >=2.5
gshtras 3c332de
Merge remote-tracking branch 'origin/main' into rocm_quantization_ena…
gshtras 2fe7a3b
Merge remote-tracking branch 'origin/main' into rocm_quantization_ena…
gshtras File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we move this is_hip() check + its proceeding code to a utils file? seems to be similar update to the weights/scales in multiple cases
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could move the input_scale adjustment into utils, as it is the one common part between the 3 quantization types that support HIP fnuz), but IMO that would make it less explicit, because different parameters of the layer (weight, weight_scale, input_scale) would be adjusted in different places in the code.
Other than that it's a single function call from utils that's specific to HIP.