fix(moe): name-filter output-scale-incompatible cubins until pinned packages carry mDtypeSfC

[Vinnie6167]

📌 Description

Fixes two coupled problems on release-v0.6.16:

1. The branch tip cannot compile the trtllm-gen fused-MoE module — on any architecture.
#4213 checks BatchedGemmOptions::mDtypeSfC, but that field does not exist in either pinned cubin package's exported headers (Blackwell b368d003, Rubin 46d3f356 — verified 0 occurrences in both published BatchedGemmOptions.h, and in the internal 81a53cff package as well). Any JIT or AOT rebuild of fused_moe_trtllm_* fails with:

trtllm_batched_gemm_runner.cu(128): error: class "BatchedGemmOptions" has no member "mDtypeSfC"

(The original PR #4168 shows the same failure in its CI on main.)

2. The FP4-MoE illegal-memory-access #4213 targets (#4164 / NVBug 6517914) is still live on Rubin.
The offending bmm_E2m1xFp32_* kernels emit linear FP32 output scale-factors into the E4M3-sized (1 B/block) buffer the MoE pipeline allocates → device-side overflow → async IMA, near-deterministic under autotune. Verified against the published catalogs: 132 such kernels, all in the sm_107a package (46d3f356); zero in the Blackwell package — which is why the per-arch pin split (#4191) healed Blackwell while Rubin still crashes.

What changed

Replace the un-compilable typed check with a kernel-name filter carrying the same intent: reject configs whose mFunctionName contains the E2m1xFp32 token. This compiles against the currently published packages and removes the bad candidates before autotune can run them. #4213's other changes (per-token-scaling restructure, launcher tactic-enumeration alignment) are inherited unchanged.

Scope note: the name filter is deliberately narrower than the typed check — it rejects only the known-bad family. Against the published catalogs this is behaviorally equivalent (the E2m1xFp32 kernels are the only offenders present). The TODO in the code ties restoring the typed mDtypeSfC check to publishing + pinning packages that carry the field.

Validation

• Build break reproduced (sbsa AOT wheel build, CTK 13.4) at the branch tip; gone with this patch.
• VR200 (Rubin) re-run of the affected MoE test files in progress; results will be posted here before marking ready for review.

Refs: #4164, #4213, #4168 · NVBug 6517914

🤖 Generated with Claude Code

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 5c676bce-d81b-47d4-8c74-272436f57b06

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[kahyunnam]

lgtm to merge for rc4 pending validation on rubin

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.