-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
[Fix][ROCm] Remove unused variables to fix build error on GFX11/12 #19891
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Hosang Yoon <[email protected]>
👋 Hi! Thank you for contributing to the vLLM project. 💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels. Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging. To run CI, PR reviewers can either: Add 🚀 |
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.
Summary of Changes
Hello @hyoon1, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request addresses a critical build failure on AMD Radeon GPUs (GFX11/12) by removing specific unused variables within the custom paged attention kernel. The changes are purely for compilation success and code cleanliness, with no impact on the functional behavior or performance of the existing attention mechanism.
Highlights
- Build Fix for ROCm: Removed unused local variables (
lane4id
andkglobal_token_idx
) from the custom paged attention kernel incsrc/rocm/attention.cu
. This resolves a build error specifically on AMD Radeon GPUs (GFX11/12) that was introduced by a previous PR. - Code Clean-up: Improved code hygiene by removing variables that were declared but not utilized, ensuring the codebase remains lean and maintainable. The changes have no functional impact.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
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.
Code Review
The pull request removes unused variables in the custom paged attention kernel to fix a build error on AMD Radeon GPUs (gfx11/12). The changes involve deleting unused local variables in the paged_attention_ll4mi_QKV_mfma16_kernel
function within the csrc/rocm/attention.cu
file. The variables lane4id
and kglobal_token_idx
are removed as they are not utilized within the kernel's logic.
@@ -1598,7 +1598,6 @@ __launch_bounds__(NUM_THREADS, 3) void paged_attention_ll4mi_QKV_mfma16_kernel( | |||
const int warpid = threadIdx.x / WARP_SIZE; | |||
const int laneid = threadIdx.x % WARP_SIZE; | |||
const int lane2id = laneid % 2; | |||
const int lane4id = laneid % 4; | |||
const int lane16id = laneid % 16; |
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.
@@ -1745,7 +1744,6 @@ __launch_bounds__(NUM_THREADS, 3) void paged_attention_ll4mi_QKV_mfma16_kernel( | |||
const cache_t* k_ptr2 = k_ptr + kblock_number * kv_block_stride; | |||
const int klocal_token_idx = | |||
TOKENS_PER_WARP * warpid + token_depth * 16 + lane16id; | |||
const int kglobal_token_idx = partition_start_token_idx + klocal_token_idx; | |||
const int kphysical_block_offset = klocal_token_idx % BLOCK_SIZE; | |||
const cache_t* k_ptr3 = k_ptr2 + kphysical_block_offset * KX; |
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.
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.
LGTM
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.
Good catch and fix, thanks
Retry the failed tests. Curious how the breakage was landed. |
Oh, my PR didn't cover the old arches... sorry. |
Essential Elements of an Effective PR Description Checklist
supported_models.md
andexamples
for a new model.Purpose
After this PR: #19796 build is failing on AMD Radeon GPU (gfx11/12)
Removed unused variables from custom paged attention kernel to fix build error
Test Plan
python setup.py develop
Test Result
Build succeeded after removing unused variables.
No functional changes.
(Optional) Documentation Update