-
-
Notifications
You must be signed in to change notification settings - Fork 8.4k
fix AiterFlashAttentionImpl init #20103
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
Conversation
👋 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 @yuguo68, 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 resolves an initialization error in the AiterFlashAttentionImpl
class, which was preventing proper instantiation for certain models like Llama4. It updates the constructor signature to include a previously missing argument and clarifies the current support for KV sharing within this attention implementation.
Highlights
- Bug Fix: Addresses a
TypeError
inAiterFlashAttentionImpl.__init__
that occurred when initializing for Llama4 models, specifically due to a missingkv_sharing_target_layer_name
argument. - API Change: The
kv_sharing_target_layer_name
argument has been added to the__init__
method ofAiterFlashAttentionImpl
to align with expected parameters from calling code. - Feature Limitation: An explicit
NotImplementedError
is now raised ifkv_sharing_target_layer_name
is provided, indicating that KV sharing is not currently supported byAiterFlashAttention
.
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. ↩
This pull request was exported from Phabricator. Differential Revision: D77340637 |
cc @houseroad to review |
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 adds the kv_sharing_target_layer_name
argument to the AiterFlashAttentionImpl
class and raises a NotImplementedError
when it is used, as KV sharing is not supported in AiterFlashAttention
. A suggestion was made to raise the NotImplementedError
earlier in the code to improve clarity.
Summary: Signed-off-by: Yu Guo <yuguo@meta.com> get error ```TypeError: AiterFlashAttentionImpl.__init__() got multiple values for argument 'use_irope'``` for llama4, AiterFlashAttentionImpl.__init__() is missing the `kv_sharing_target_layer_name` arg, https://github.com/vllm-project/vllm/blob/296ce95d8e72f4c6680bda539058f48dbe0f340a/vllm/attention/layer.py#L54 Test Plan: launch a llama4 server with this fix Rollback Plan: Differential Revision: D77340637
568cb85
to
5933173
Compare
This pull request was exported from Phabricator. Differential Revision: D77340637 |
Summary: Pull Request resolved: vllm-project#20103 Signed-off-by: Yu Guo <yuguo@meta.com> get error ```TypeError: AiterFlashAttentionImpl.__init__() got multiple values for argument 'use_irope'``` for llama4, AiterFlashAttentionImpl.__init__() is missing the `kv_sharing_target_layer_name` arg, https://github.com/vllm-project/vllm/blob/296ce95d8e72f4c6680bda539058f48dbe0f340a/vllm/attention/layer.py#L54 Test Plan: launch a llama4 server with this fix Rollback Plan: Differential Revision: D77340637
5933173
to
bbdde69
Compare
Summary: Signed-off-by: Yu Guo <yuguo@meta.com> get error ```TypeError: AiterFlashAttentionImpl.__init__() got multiple values for argument 'use_irope'``` for llama4, AiterFlashAttentionImpl.__init__() is missing the `kv_sharing_target_layer_name` arg, https://github.com/vllm-project/vllm/blob/296ce95d8e72f4c6680bda539058f48dbe0f340a/vllm/attention/layer.py#L54 Test Plan: launch a llama4 server with this fix Rollback Plan: Differential Revision: D77340637
bbdde69
to
fa88b14
Compare
Summary: Pull Request resolved: vllm-project#20103 Signed-off-by: Yu Guo <yuguo@meta.com> get error ```TypeError: AiterFlashAttentionImpl.__init__() got multiple values for argument 'use_irope'``` for llama4, AiterFlashAttentionImpl.__init__() is missing the `kv_sharing_target_layer_name` arg, https://github.com/vllm-project/vllm/blob/296ce95d8e72f4c6680bda539058f48dbe0f340a/vllm/attention/layer.py#L54 Test Plan: launch a llama4 server with this fix Rollback Plan: Differential Revision: D77340637
This pull request was exported from Phabricator. Differential Revision: D77340637 |
fa88b14
to
875dcc0
Compare
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.
Thanks for the fix!
Can you list the test plan in the PR description as well?
use_irope: bool = False, | ||
) -> None: | ||
if blocksparse_params is not None: | ||
raise ValueError( | ||
"AiterFlashAttention does not support block-sparse attention.") | ||
if kv_sharing_target_layer_name is not None: |
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.
Nit: also check it’s not empty string?
@yuguo68 @houseroad This fix is also addressed in this PR #19904 . Overall, the AITER Flash Attention Backend requires a few fixes in this PR #19904. |
Summary: get error
TypeError: AiterFlashAttentionImpl.__init__() got multiple values for argument 'use_irope'
for llama4, AiterFlashAttentionImpl.init() is missing thekv_sharing_target_layer_name
arg,vllm/vllm/attention/layer.py
Line 54 in 296ce95
Test Plan:
launch a llama4 server with this fix
Rollback Plan:
Differential Revision: D77340637