vllm - 💡(How to fix) Fix [Feature]: Support DFlash for Kimi K2.5 and Qwen3.5-27B for AMD [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vllm-project/vllm#40632Fetched 2026-04-23 07:23:42
View on GitHub
Comments
2
Participants
3
Timeline
13
Reactions
0
Assignees
Timeline (top)
mentioned ×3subscribed ×3commented ×2labeled ×2
RAW_BUFFERClick to expand / collapse

🚀 The feature, motivation and pitch

Feature Proposal Description Enable support for non-causal attention in AMD backends to allow diffusion-based speculative decoders like DFlash (used with models such as Kimi-K2.5 and Qwen 3.5-27B) to run successfully on AMD hardware.

Motivation DFlash is a diffusion-based speculative decoding approach with vLLM support that currently works on NVIDIA GPUs but fails on AMD platforms. This limits the usability of emerging decoding techniques and models (e.g., Kimi-K2.5, Qwen3.5-27B) within the AMD ecosystem, creating a feature gap compared to competing hardware. This feature/models works fine on Nvidia

Alternatives

No response

Additional context

No response

Before submitting a new issue...

  • Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

extent analysis

TL;DR

Enable support for non-causal attention in AMD backends to allow diffusion-based speculative decoders like DFlash to run on AMD hardware.

Guidance

  • Investigate the current implementation of attention mechanisms in the AMD backend to identify potential modifications for supporting non-causal attention.
  • Research the specific requirements of DFlash and similar diffusion-based speculative decoders to ensure compatibility with the proposed feature.
  • Consider collaborating with developers of DFlash or similar models to ensure a comprehensive understanding of the necessary changes.
  • Evaluate the feasibility of implementing non-causal attention in the AMD backend without compromising performance or introducing significant complexity.

Notes

The solution may require significant modifications to the existing AMD backend implementation, and careful consideration of performance and complexity trade-offs is necessary.

Recommendation

Apply a workaround by collaborating with the DFlash developers to implement a model-specific solution that can run on AMD hardware, as a full feature implementation may require substantial changes to the AMD backend.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

vllm - 💡(How to fix) Fix [Feature]: Support DFlash for Kimi K2.5 and Qwen3.5-27B for AMD [2 comments, 3 participants]