-
-
Notifications
You must be signed in to change notification settings - Fork 10.7k
[BugFix][AMD] Compatible patch for latest AITER(05/07/2025) #17864
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
Signed-off-by: Qiang Li <qiang.li2@amd.com>
👋 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 🚀 |
Hi, @qli88: |
Any tests in this PR? |
The incompatibility is caused by mainly 2 things: 1. AITER MoE interface changes; 2. AITER MLA interface changes. So I think this is irrelevant to base docker image. |
This change is for ROCm only and I have tested on MI300X host with DeepSeek V3. |
The reason I am asking about from which commit of aiter introduced those changes. If the customer currently only uses upstream to build from source to serve Deepseek model, does the current aiter commit (https://github.com/vllm-project/vllm/blob/main/docker/Dockerfile.rocm_base#L15) in Dockerfile.rocm_base works with these changes? |
Thanks for the context! I think the new Docker image that will be released today (or tomorrow) will use the AITER commit I mentioned above (commit c1debd87ce0391aa27438d9e07e76e4fea7c4b70). |
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.
Looks reasonable to me but will wait for @SageMoore to sign off
This PR introduces two undefined names vllm/vllm/attention/ops/rocm_aiter_mla.py Lines 63 to 72 in 200da9a
https://github.com/vllm-project/vllm/actions/runs/14931789556 |
Darn, why did the precommit not show up in the checks? |
Yeah it's all green here, perhaps it was just a race condition with another PR that didn't trigger merge conflicts? |
…ject#17864) Signed-off-by: Qiang Li <qiang.li2@amd.com> Signed-off-by: David Xia <david@davidxia.com>
Looks like vllm-project#17864 had an outdated branch. So its [merge commit][1] caused `qo_indptr` and `max_seqlen_qo` to go into the function signature of `aiter_mla_decode_fwd()` where they're not used and into the body of `mla_decode_fwd_impl()` where they aren't defined. This PR fixes the discrepancies and call-sites. [1]: vllm-project@9f64e93#diff-88fd09f50e8cfc77678ade87483ab9a89ce58904203578f8816882763bd577c2 Signed-off-by: David Xia <david@davidxia.com>
…ject#17864) Signed-off-by: Qiang Li <qiang.li2@amd.com> Signed-off-by: 汪志鹏 <wangzhipeng628@gmail.com>
…ject#17864) Signed-off-by: Qiang Li <qiang.li2@amd.com> Signed-off-by: Mu Huai <tianbowen.tbw@antgroup.com>
…ject#17864) Signed-off-by: Qiang Li <qiang.li2@amd.com>
…ject#17864) Signed-off-by: Qiang Li <qiang.li2@amd.com> Signed-off-by: Yuqi Zhang <yuqizhang@google.com>
This PR is for AITER API changes introduced by commit 939f741fc37f46694e48c32c7164f49eae2584c4 (merged on 04/20/2025). AITER versions after this require this patch to work.