-
Notifications
You must be signed in to change notification settings - Fork 217
[AMD] MiniMax-M3 FP4/FP8 MI355X ATOM: refactor config & add MTP recipes #2001
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+27
−12
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔴 This PR bumps the ATOM image, swaps env vars, and adds a new
--online_quant_configflag across all fourminimaxm3-*-mi355x-atomrecipes, but does not append aperf-changelog.yamlentry. AGENTS.md's "Updating Docker images" section (line 126) explicitly states an entry is required — triggers benchmarks, and without it the four sweeps listed in this PR's own test-plan checklist will not run automatically in CI. Please append a changelog block listing the four affected config-keys (minimaxm3-fp4-mi355x-atom,minimaxm3-fp4-mi355x-atom-mtp,minimaxm3-fp8-mi355x-atom,minimaxm3-fp8-mi355x-atom-mtp), mirroring the pattern used in PRs #1978 and #1990 at the tail of the file.Extended reasoning...
What is missing. The PR touches five files (
configs/amd-master.yamland the fourbenchmarks/single_node/fixed_seq_len/minimaxm3_*_mi355x_atom*.shscripts) but does not modifyperf-changelog.yaml. The changes made across those five files are exactly the kind that AGENTS.md flags as changelog-triggering:rocm/atom-dev:MiniMax-M3-20260623→rocm/atom-dev:nightly_202607011530(configs/amd-master.yaml:2648, 2667, 2686, 2705)..shscripts: removesAITER_QUICK_REDUCE_CAST_BF16_TO_FP16=0andATOM_M3_SPARSE_USE_ASM_PA=1, addsATOM_FORCE_ATTN_TRITON=1..shscripts: adds--online_quant_config(ptpc_fp8 with MoE exclusion list) via the newOPT_ARGSarray.Why this is required, not optional. AGENTS.md is unambiguous. Line 15:
perf-changelog.yaml - benchmark trigger log; append-only. Line 58:Changes to perf-changelog.yaml trigger benchmark runs. And lines 124–126 (§ Updating Docker images): Update the image tag in the relevant configs/*-master.yaml and/or benchmarks/*.sh, update any related env vars / config params, and append a perf-changelog.yaml entry (required - triggers benchmarks).Concrete consequence for this PR. The PR test-plan lists four sweeps that must be validated before merge:
minimaxm3-fp4-mi355x-atom,minimaxm3-fp4-mi355x-atom-mtp,minimaxm3-fp8-mi355x-atom,minimaxm3-fp8-mi355x-atom-mtp. Becauseperf-changelog.yamlis the mechanism that tells the sweep runner which configs to benchmark for this PR, and no entry was added, none of those four sweeps will fire automatically. The PR ships an image + env/flag change that has never been validated in this repo's CI.Step-by-step proof.
perf-changelog.yaml.configs/amd-master.yamlandbenchmarks/single_node/fixed_seq_len/*.sh) is what that section describes.perf-changelog.yamlat HEAD: PR Update Minimax M3 FP4 vllm #1978 (minimaxm3-fp4-b200-vllmimage bump) and [NV] perf: update MiniMax-M3 FP4 B300 vLLM #1990 (minimaxm3-fp4-b300-vllmimage bump) each appended a block withconfig-keys, adescription, and apr-link. This is the pattern to follow.perf-changelog.yamlchronologically to determine whichconfig-keysthis PR modified) sees zero new keys and skips all four MiniMax-M3 ATOM sweeps.How to fix. Append a block to the end of
perf-changelog.yaml(preserving its append-only whitespace convention — see AGENTS.md:150) along the lines of:That single append unblocks the four sweeps in the PR's own test plan.