Skip to content

Conversation

@ProExpertProg
Copy link
Collaborator

@ProExpertProg ProExpertProg commented Aug 13, 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

Test Plan

Test Result

(Optional) Documentation Update

Signed-off-by: Luka Govedic <[email protected]>
@github-actions
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.

🚀

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 refactors the FP8 quantization logic to use a QuantFP8 module, which is a good abstraction. The fusion passes are updated accordingly to match this new pattern. While the changes are generally moving in the right direction, I've identified a few critical issues, including commented-out code that disables functionality or tests, and leftover debugging statements. These should be addressed before this pull request can be merged.

Comment on lines +1139 to +1163
# if current_platform.has_device_capability(100):
# AllReduceFusedRMSNormStaticQuantNVFP4Pattern(
# epsilon,
# self.model_dtype,
# self.device,
# self.allreduce_params,
# ).register(self.patterns)
# AllReduceFusedAddRMSNormStaticQuantNVFP4Pattern(
# epsilon,
# self.model_dtype,
# self.device,
# self.allreduce_params,
# ).register(self.patterns)
# AllReduceRMSNormPattern(
# epsilon,
# self.model_dtype,
# self.device,
# self.allreduce_params,
# ).register(self.patterns)
# AllReduceFusedAddRMSNormPattern(
# epsilon,
# self.model_dtype,
# self.device,
# self.allreduce_params,
# ).register(self.patterns)
Copy link
Contributor

Choose a reason for hiding this comment

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

critical

This large block of commented-out code disables several fusion patterns, including those for FP4 and non-quantized RMSNorm. This appears to be a significant functional regression. If this is a temporary change for development, it should be reverted before merging. If this is intentional, it needs a clear justification.

torch.testing.assert_close(result, result2, atol=ATOL, rtol=RTOL)

# In pre-nodes, fp8 quant should be there and fused kernels should not
# backend.check_before_ops(model.ops_in_model_before())
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 assertion is commented out. In test files, assertions should not be commented out as it can hide regressions or bugs. If this check is failing, it should be investigated and fixed. Please either re-enable this check or provide a justification for its removal.

Comment on lines +233 to +240
print(backend.graph_pre_pass)
print(backend.graph_post_pass)
for node in find_op_nodes(
torch.ops.vllm.flashinfer_trtllm_fused_allreduce_norm.default,
backend.graph_post_pass):
print(f"{node.args=}")
print(f"{node.kwargs=}")

Copy link
Contributor

Choose a reason for hiding this comment

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

high

These print statements and the following loop appear to be debugging code. They should be removed before merging to keep the test output clean.

@ProExpertProg ProExpertProg force-pushed the luka/torch-custom-op-pattern branch from 6374e53 to 5eeb376 Compare August 19, 2025 16:11
Signed-off-by: Luka Govedič <[email protected]>
@mergify
Copy link

mergify bot commented Aug 28, 2025

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @ProExpertProg.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

@ProExpertProg
Copy link
Collaborator Author

Superseeded by #24604

@github-project-automation github-project-automation bot moved this from In progress to Done in torch.compile integration Sep 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant