Skip to content

Conversation

Adolfo-Karim
Copy link
Contributor

@Adolfo-Karim Adolfo-Karim commented May 28, 2025

Signed-off-by: Adolfo Victoria [email protected]

Summary: When calling create_engine_config we don't respect the device set in engine args and instead grab it from the runtime platform directly. This logic is also extraneous since the default behavior (i.e. device=auto) is to set the device to the runtime platform device if auto is passed inside of __post_init__ inside of DeviceConfig

Differential Revision: D75496412

Copy link

👋 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 fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

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 ready label to the PR or enable auto-merge.

🚀

@facebook-github-bot
Copy link

This pull request was exported from Phabricator. Differential Revision: D75496412

Summary:
Signed-off-by: Adolfo Victoria [email protected]

When calling `create_engine_config` we don't respect the device set in engine args and instead grab it from the runtime platform directly. This logic is also extraneous since the default behavior (i.e. device=auto) is to set the device to the runtime platform device if auto is passed inside of `__post_init__` inside of `DeviceConfig`

Differential Revision: D75496412
@facebook-github-bot
Copy link

This pull request was exported from Phabricator. Differential Revision: D75496412

current_platform.pre_register_and_update()

device_config = DeviceConfig(device=current_platform.device_type)
device_config = DeviceConfig(device=self.device)
Copy link
Member

Choose a reason for hiding this comment

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

We have already deprecated the --device argument in #18399 after multiple platform plugin authors agreed to it. Could you elaborate on how this is used in your application? cc @youkaichao

Copy link
Collaborator

Choose a reason for hiding this comment

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

Seems we intentionally make "device" arg not honored. Wondering @Adolfo-Karim , do we need to use "device" in EngineArg for something?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Discuss offline with @Adolfo-Karim , it's more like a "CPU" deterministic logic.

Copy link
Member

Choose a reason for hiding this comment

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

"CPU" deterministic logic

what does this mean?

Copy link
Collaborator

Choose a reason for hiding this comment

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

https://github.com/vllm-project/vllm/blob/main/vllm/platforms/__init__.py#L156, here, we check the "CPU" in the package name. We don't actually have package, since we use monolithic / unified codebase.

@houseroad
Copy link
Collaborator

I guess we probably can close this PR per discussion with @Adolfo-Karim , likely we will solve this issue with internal workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants