[Ascend] support qwen3.5 35BA3B#4485
Merged
lvhan028 merged 10 commits intoInternLM:mainfrom Apr 8, 2026
Merged
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
jinminxi104
approved these changes
Apr 7, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Adds Ascend/DLinfer support plumbing needed to run Qwen3.5 35B A3B (notably the linear-attention / gated-delta path) by propagating device_type, extending attention metadata, and initializing Ascend-specific Triton device properties.
Changes:
- Propagate
device_typeinto HF→ModelConfig build path and use it to pick bf16/fp16 state dtypes for Qwen3.5 configs. - Extend DLInfer attention metadata and populate Ascend attention metadata with GDN-related sequence info.
- Add Ascend backend initialization for Triton device properties with fallback warnings when triton-ascend is missing.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| lmdeploy/pytorch/configurations/qwen3_5.py | Use device_type when selecting bf16 vs fp16 for Qwen3.5 state caches. |
| lmdeploy/pytorch/config.py | Thread device_type through ModelConfig.from_hf_config into the model config builder. |
| lmdeploy/pytorch/backends/dlinfer/attention.py | Add has_initial_state field to DLInfer attention metadata. |
| lmdeploy/pytorch/backends/dlinfer/ascend/op_backend.py | Populate GDN sequence metadata and initialize Triton device properties for Ascend backend. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily receiving feedbacks. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist