-
Notifications
You must be signed in to change notification settings - Fork 22k
GGML/llama.cpp: Add scaled GEMMs for more robust NVFP4 support #23484
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
Closed
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
7ea0c17
Add support for derived tensors to mul_mat and mul_mat_id
ORippler 906c396
llama: start routeing derived matmul scales via ext API
ORippler 811110c
Rename is_derived -> needs_scale, add comment
ORippler 4c03b5a
Add error logs to ggml_mul_mat and ggml_mult_mat_ext
ORippler 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
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.
My opinion is that it is preferable not to change
GGML_OP_MUL_MATand to instead construct theggml_grapharound it in such a way that prevents an accidental misuse of NVFP4.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.
Agreed. I tried, but failed to make this work with the optional
input_scaleconsumption we would like to have available for W4A4 on NVGPUs. Afaik, GGML doesn't prescribe to a backend whether to promote or downcast its inputs during GEMMs. Here, only backends that use NVFP4 hardware-accelerators will need a pre-div/post-mul withinput_scalefor the W4A4 path to maintain accuracy. Hence, this needs to be optional:graph LR A[NVFP4 weights] --> B{GGML_OP_MUL_MAT} C[FP32 activations] --> B D[F32 weights_post_scale] --> B E[F32 activations_pre_post_scale] -.-> B B --> F{non-linearity, <br> e.g. SwiGLU}Definitely open to suggestions on how to fully represent this optionality at the
ggml_cgraphlevel. I refrained from always pre-div/post-muling, as I thought it to be the more intrusive and thus worse approach - maybe you disagree on this?