Extra_options disable_qkv_fusion to untie qkv_projs from upstream choice
#1893
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.
Problem
As we discussed in this PR, I separate
disable_qkv_fusionoption as a new PR.The current model builder ties q_proj, k_proj and v_proj together as qkv_proj by default, which is not controllable by upstream quantization choice.
Solution
Added
disable_qkv_fusionin extra_options to overrideattention_attrs["use_packed_matmul"].Running examples:
untied qvk_projs for 4 bit rtn on Llama-3.2-3B-Instruct:
Changes
Modified Files
src/python/py/models/builder.pysrc/python/py/models/builders/base.pysrc/python/py/models/README.MDKey Modifications
disable_qkv_fusionas a part of assigning logic ofattention_attrs["use_packed_matmul"].