-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
[Feat][DSV4] Fuse q pad into deepseek v4 fused kernel #43162
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
zyongye:feat/fuse-q-pad-into-deepseek-v4-fused-kernel
May 26, 2026
Merged
Changes from 7 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
d499fda
[Kernel] Fuse Q head-pad into DeepSeek V4 fused QNorm/RoPE/KV-insert
f58f03c
[Kernel] Add 8/16/32 head dispatch to DeepSeek V4 fused QNorm/RoPE/KV…
zyongye 844840f
[Kernel][Test] Cover 8/16/32 head dispatch in fused DeepSeek V4 tests
zyongye 0c2f37a
[Refactor] Move DeepSeek V4 attention.py out of nvidia/ subdir
zyongye 3f99d06
[CI] Run fused DeepSeek V4 QNorm/RoPE/KV-insert test in Kernels Core …
zyongye 909b732
[CI] Add Deepseek V4 Kernel Test category on H100 and B200
zyongye 19276a6
Merge branch 'main' into feat/fuse-q-pad-into-deepseek-v4-fused-kernel
zyongye ecf2bcc
updates
zyongye 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
Large diffs are not rendered by default.
Oops, something went wrong.
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.
On ROCm,
get_padded_num_q_headscurrently returnsnum_headswithout any padding. However, the horizontally-fused preprocessing kernel (fused_deepseek_v4_qnorm_rope_kv_rope_quant_insert) is shared between NVIDIA and ROCm, and its dispatch logic (incsrc/fused_deepseek_v4_qnorm_rope_kv_insert_kernel.cu) only supportskNumHeadsQPaddedvalues of 64 and 128. This will cause a runtime crash on ROCm for any configuration wherenum_headsis not exactly 64 or 128 (e.g., TP=4 wherenum_heads=32). To ensure compatibility with the fused kernel's template instantiations, ROCm should use the same padding logic as NVIDIA.