mirror of
https://github.com/deepseek-ai/DeepGEMM.git
synced 2026-11-05 00:47:26 +00:00
[PR #113] [MERGED] Fix illegal memory address when skipping -1 m indices #248
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/DeepGEMM#248
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/deepseek-ai/DeepGEMM/pull/113
Author: @shixianc
Created: 6/15/2025
Status: ✅ Merged
Merged: 6/16/2025
Merged by: @LyricZhao
Base:
main← Head:main📝 Commits (1)
b7ccb13Fix illegal memory address when skipping -1 m indices📊 Changes
1 file changed (+1 additions, -1 deletions)
View changed files
📝
deep_gemm/include/deep_gemm/scheduler.cuh(+1 -1)📄 Description
I'm testing vllm integration with latest
m_grouped_gemm_fp8_fp8_bf16_nt_contiguousbut I faced an issue when I pad m_indices with-1for skipping useless compute.When VLLM tries to capture the whole CUDA Graph for the model, it fails with error
However if I benchmark this kernel separately it passes with -1. After debugging this is related to tma_copy operation at this line.
scheduler.get_global_idxwill return an invalid index for -1 m block.With the changes in the PR it fixes the issue. However after some research, it seems invalid address is an no-op for tma_copy, and maybe by design to skip useless loading? Because if I benchmark this kernel separately it passes with -1.
Can anyone help clarifying this and suggest on the different behavior by CUDA Graph capturing? Thanks!!
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.