Skip to content

Conversation

seemethere
Copy link
Contributor

@seemethere seemethere commented Jul 18, 2025

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.

Purpose

Adds CUDA + arm64 builds

Test Plan

CI

Test Result

(Optional) Documentation Update

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.

🚀

@mergify mergify bot added the ci/build label Jul 18, 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 adds a new Buildkite CI step to build a release wheel for arm64 with CUDA 12.9. The torch_cuda_arch_list build argument in the docker build command does not include CUDA compute capabilities 10.0 or 12.0, which should be added to ensure compatibility.

Copy link
Contributor

Choose a reason for hiding this comment

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

high

This arm64 build step will likely fail because the torch_cuda_arch_list build argument in the docker build command does not include CUDA compute capabilities 10.0 or 12.0. These architectures should be added to ensure compatibility with the target CUDA version and architecture.

"DOCKER_BUILDKIT=1 docker build --build-arg max_jobs=16 --build-arg USE_SCCACHE=1 --build-arg GIT_REPO_CHECK=1 --build-arg CUDA_VERSION=12.9.1 --build-arg torch_cuda_arch_list='7.0 7.5 8.0 8.9 9.0 10.0 12.0+PTX' --tag vllm-ci:build-image --target build --progress plain -f docker/Dockerfile ."

@mgoin mgoin changed the title ci: Add CUDA + arm64 relase builds ci: Add CUDA + arm64 release builds Jul 18, 2025
Copy link
Member

@mgoin mgoin Jul 18, 2025

Choose a reason for hiding this comment

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

For the arches, I think we only need to include the ones that compute capabilities that have SKUs with ARM CPUs

Referencing https://developer.nvidia.com/cuda-gpus, I think that is mostly GH200 and GB200, which are 9.0 and 10.0 respectively. We could include 8.7 to cover the Jetson boards as well.

So I am proposing torch_cuda_arch_list='8.7 9.0 10.0+PTX'

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This sounds reasonable to me

@sara4dev
Copy link

sara4dev commented Aug 6, 2025

can we get this reviewed & merged?

@nvpohanh
Copy link
Contributor

@seemethere could you fix the DCO issue? thanks

@nvpohanh
Copy link
Contributor

@seemethere Could you rebase this PR and fix the DCO issue? Thanks!

Copy link
Member

Choose a reason for hiding this comment

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

Is this for torch 2.7.0? Does this change for 2.7.1 or 2.8.0?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is still the case for all PyTorch releases today afaik

seemethere and others added 2 commits August 13, 2025 10:25
@seemethere seemethere force-pushed the seemethere/cuda_arm64 branch from 575304e to 846aa6d Compare August 13, 2025 17:26
@seemethere
Copy link
Contributor Author

@seemethere Could you rebase this PR and fix the DCO issue? Thanks!

Rebased + DCO should be fixed now!

@simon-mo simon-mo added this to the v0.10.1 milestone Aug 13, 2025
@seemethere
Copy link
Contributor Author

q: how do we actually run this?

@simon-mo
Copy link
Collaborator

buildkite, release pipeline, run with this branch and commit

@mgoin mgoin mentioned this pull request Aug 13, 2025
4 tasks
Also explicitly sets VLLM_TARGET_DEVICE as an environment variable

Signed-off-by: Eli Uriegas <[email protected]>
@seemethere seemethere force-pushed the seemethere/cuda_arm64 branch from 1895656 to cf453f3 Compare August 13, 2025 23:22
@seemethere
Copy link
Contributor Author

buildkite, release pipeline, run with this branch and commit

Will this actually work on a forked PR?

@simon-mo simon-mo enabled auto-merge (squash) August 15, 2025 01:59
@github-actions github-actions bot added the ready ONLY add when PR is ready to merge/full CI is needed label Aug 15, 2025
@simon-mo
Copy link
Collaborator

simon-mo commented Aug 15, 2025

Copy link
Member

@mgoin mgoin left a comment

Choose a reason for hiding this comment

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

🥳

@simon-mo simon-mo merged commit 76144ad into vllm-project:main Aug 15, 2025
72 checks passed
666even666 pushed a commit to 666even666/vllm that referenced this pull request Aug 18, 2025
yiliu30 pushed a commit to yiliu30/vllm-fork that referenced this pull request Aug 19, 2025
divakar-amd pushed a commit to divakar-amd/vllm_upstream that referenced this pull request Aug 20, 2025
djmmoss pushed a commit to djmmoss/vllm that referenced this pull request Aug 21, 2025
epwalsh pushed a commit to epwalsh/vllm that referenced this pull request Aug 28, 2025
xiao-llm pushed a commit to xiao-llm/vllm that referenced this pull request Aug 28, 2025
zhewenl pushed a commit to zhewenl/vllm that referenced this pull request Aug 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci/build ready ONLY add when PR is ready to merge/full CI is needed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants