-
Notifications
You must be signed in to change notification settings - Fork 525
Add TensorQuantizer rotate-back mode #1879
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
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
1294df6
Add TensorQuantizer rotate-back mode
realAsma 28deef1
Add Hadamard roundtrip GPU test
realAsma b2f5fc8
Address rotate-back review feedback
realAsma de15abf
Refine TensorQuantizer rotate-back handling
realAsma e0c70b3
Address tensor quantizer rotation review comments
realAsma b82e5e8
Add W4A4 rotate eval config workaround
realAsma 7ec1afc
Clear rotation when disabling tensor quantizers
realAsma d4cda04
Remove temporary W4A4 rotate eval config
realAsma 5de9683
Move rotate.mode changelog entry under features
realAsma a600718
Test rotation-enabled quantizer backward
realAsma 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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
It is not very clear to me what the use cases are for the different modes. Can you elaborate?
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.
Thanks — the distinction is about whether the quantizer changes the tensor's basis:
rotate: computesQ(Hx)and leaves the output in the Hadamard-rotated basis. This is for flows where the surrounding graph compensates for that basis change (for example, pairing activation rotation with a correspondingly folded/rotated linear weight). It is also the existing behavior, so it remains the default for backward compatibility.rotate_back: computesH Q(Hx)(the normalized Hadamard transform is self-inverse), so quantization still benefits from the rotated-domain value distribution but the quantizer output returns to the original basis. This is the drop-in choice when downstream operators should remain unchanged.rotate_backis currently fake-quant-only because a real quantized tensor cannot be inverse-rotated through the existing quantized representation/backend.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.
rotate without rotate back only: Requires the complimentary operation also to be rotated. (example : weight_quantizer rotate -> activation quantizer should also rotate, otherwise model will produce garbage.)
rotate with rotate back: The op is rotated -> quantized -> rotated back ; Does not need complimentary op to be rotated to be functionally correct.