Skip to content

Conversation

Isotr0py
Copy link
Member

@Isotr0py Isotr0py commented Sep 22, 2025

Purpose

  • Since V0 has been removed, I think there is no need to keep supports_v1 and default_v1 to control v0 fallback at platform level

Also cc @Yikun @xuechendi in case these interfaces are still used by plugins.

Test Plan

Test Result


Essential Elements of an Effective PR Description Checklist
  • The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
  • The test plan, such as providing test command.
  • The test results, such as pasting the results comparison before and after, or e2e results
  • (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.
  • (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

Signed-off-by: Isotr0py <mozf@mail2.sysu.edu.cn>
Signed-off-by: Isotr0py <mozf@mail2.sysu.edu.cn>
@mergify mergify bot added rocm Related to AMD ROCm v1 tpu Related to Google TPUs labels Sep 22, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request removes the supports_v1 and default_v1 methods from the platform interfaces, aiming to clean up V0 deprecation-related code. The changes are consistent across the codebase, removing the method definitions and their usages. However, this change removes a safeguard that prevented V1 from being enabled on new or untested platforms. I've raised a critical concern about the potential for enabling V1 on incompatible platforms, which could lead to runtime issues. It's important to clarify whether V0 is fully removed, as this would dictate whether more V0-related fallback logic should be cleaned up, or if a new safeguard is needed.

@WoosukKwon WoosukKwon added the ready ONLY add when PR is ready to merge/full CI is needed label Sep 23, 2025
@WoosukKwon WoosukKwon enabled auto-merge (squash) September 23, 2025 00:04
@WoosukKwon WoosukKwon merged commit 6fa78d8 into vllm-project:main Sep 23, 2025
58 of 60 checks passed
linfeng-yuan pushed a commit to linfeng-yuan/vllm that referenced this pull request Sep 23, 2025
@Isotr0py Isotr0py deleted the platform-v1-flags branch September 23, 2025 05:04
FeiDaLI pushed a commit to FeiDaLI/vllm that referenced this pull request Sep 25, 2025
charlifu pushed a commit to ROCm/vllm that referenced this pull request Sep 25, 2025
…t#25410)

Signed-off-by: Isotr0py <mozf@mail2.sysu.edu.cn>
Signed-off-by: charlifu <charlifu@amd.com>
yewentao256 pushed a commit that referenced this pull request Oct 3, 2025
Signed-off-by: Isotr0py <mozf@mail2.sysu.edu.cn>
Signed-off-by: yewentao256 <zhyanwentao@126.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready ONLY add when PR is ready to merge/full CI is needed rocm Related to AMD ROCm tpu Related to Google TPUs v1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants