Repository navigation
[MM] Keep device input normalization fused when encoder compilation is enabled - #59195
Conversation
Assisted-by: OpenAI Codex Signed-off-by: Jakub Zakrzewski <jzakrzewski@nvidia.com>
| *, | ||
| enforce_enable: bool = False, | ||
| ): | ||
| super().__init__() | ||
| super().__init__(enforce_enable=enforce_enable) |
There was a problem hiding this comment.
Let's always enable fusion for this ops directly like mhc:
vllm/vllm/model_executor/layers/mhc.py
Lines 118 to 120 in 998490c
There was a problem hiding this comment.
ok, modified this PR to enable it unconditionally
Co-authored-by: Codex <codex@openai.com> Signed-off-by: Jakub Zakrzewski <jzakrzewski@nvidia.com>
|
/ci run |
|
/ci run --allow-stale |
|
❌ This PR is 9 commits behind upstream |
|
✅ Triggered Buildkite CI #91856 for commit
|
|
/ci run |
|
✅ Triggered Buildkite CI #92103 for commit |
Purpose
Keep device input normalization on its fused kernel when compile_mm_encoder=True.
Encoder compilation changes the default
custom_opssetting tonone. Pixtral’spixtral_patch_embed()runs outside the compiled transformer blocks, so Inductor cannot fuse its normalization call. Without this change,FusedMMInputNormfalls back to the eager PyTorch path.Test Plan
Test Result
Essential Elements of an Effective PR Description Checklist
supported_models.mdandexamplesfor a new model.