Skip to content

Conversation

hongxiayang
Copy link
Collaborator

@hongxiayang hongxiayang commented Aug 24, 2025

Purpose

Start to add AMD code reviewers for ROCm only components.

AITER folks would like to review aiter related component like: vllm/v1/attention/backends/rocm_aiter_fa.py to reduce the possibility of unvalidated changes which can cause regression or broken of workflows.

Currently there is only one person with write access, and he will need to ping other folks to help code review when needed.

Potentially, to add workflow rule to notify more folks in the future.

Test Plan

Test Result

(Optional) Documentation Update


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.

@mergify mergify bot added ci/build rocm Related to AMD ROCm labels Aug 24, 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 begins adding AMD code reviewers to ROCm components in the CODEOWNERS file. The changes are a good first step. My review suggests expanding the list of ROCm-related files and directories to ensure more comprehensive code ownership and review coverage, and provides a direct code suggestion to improve the current change.

Comment on lines 82 to 85
# ROCm related
/docker/Dockerfile.rocm @gshtras @hongxiayang
/docker/Dockerfile.rocm_base @gshtras @hongxiayang
/vllm/v1/attention/backends/rocm_aiter_fa.py @gshtras @hongxiayang @fsx950223
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 is a great start for adding ROCm code owners. To make it more comprehensive, I've suggested adding ownership for the entire csrc/rocm/ directory and used a wildcard for the Dockerfiles. You might also want to consider adding owners for other important files like vllm/platforms/rocm.py, ROCm-related requirements (/requirements/rocm*.txt), and tests (/tests/kernels/**/test_rocm_*.py) in a follow-up or in this PR.

# ROCm related
/docker/Dockerfile.rocm* @gshtras @hongxiayang
/csrc/rocm/ @gshtras @hongxiayang
/vllm/v1/attention/backends/rocm_aiter_fa.py @gshtras @hongxiayang @fsx950223

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

nice review comment from the gemini-code-assist bot

Copy link
Contributor

Choose a reason for hiding this comment

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

Thank you for the kind words! I'm glad I could provide helpful suggestions.

@hmellor
Copy link
Member

hmellor commented Aug 24, 2025

Codeowners must have write access to the repository, @hongxiayang @fsx950223 do not have this.

@hongxiayang
Copy link
Collaborator Author

Codeowners must have write access to the repository, @hongxiayang @fsx950223 do not have this.

Thanks for the comment. However, folks in AMD would like to get notified when certain files are changed in the pull requests, and would like to review the code promptly to avoid problems later. Unfortunately, most of them don't have write access.

What are the alternatives you wound recommend? @DarkLight1337

@DarkLight1337
Copy link
Member

I suggest having one person (with write access) to receive and forward CODEOWNERS pings.

@hmellor
Copy link
Member

hmellor commented Aug 26, 2025

Yes, @gshtras does have write access as a member of the vLLM committer team. He can forward CODEOWNER notifications to the relevant people.

Signed-off-by: Hongxia Yang <[email protected]>
@hongxiayang
Copy link
Collaborator Author

ok, @DarkLight1337 @hmellor Kindly to merge it when it is good to go. thanks.

@vllm-bot vllm-bot merged commit 1fdc732 into vllm-project:main Aug 26, 2025
5 of 9 checks passed
@hongxiayang
Copy link
Collaborator Author

cc @gshtras @fsx950223

tc-mb pushed a commit to tc-mb/vllm that referenced this pull request Aug 27, 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
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
dumb0002 pushed a commit to dumb0002/vllm that referenced this pull request Aug 28, 2025
2015aroras pushed a commit to 2015aroras/vllm that referenced this pull request Aug 29, 2025
nopperl pushed a commit to pfnet/vllm that referenced this pull request Sep 3, 2025
MatthewBonanni pushed a commit to MatthewBonanni/vllm that referenced this pull request Sep 3, 2025
MatthewBonanni pushed a commit to MatthewBonanni/vllm that referenced this pull request Sep 3, 2025
842974287 pushed a commit to 842974287/vllm that referenced this pull request Sep 3, 2025
zhewenl pushed a commit to zhewenl/vllm that referenced this pull request Sep 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci/build rocm Related to AMD ROCm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants