Add Kimi K2 target integration path#4
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed
Why
Kimi K2 Thinking is an official open-weight trillion-parameter sparse MoE target with documented MLA/SwiGLU semantics. The project can now admit only checkpoint artifacts that match the target contract while keeping hardware-dependent compatibility certification gated on actual ROCm and real-checkpoint fixtures.
Validation
python -m pytest -q— 18 passedpython -m ruff check .— passedpython -m build— source distribution and wheel builtNon-claims
This does not claim Kimi K2 compatibility, MFMA performance, or GPUDirect RoCE. The release gates require target hardware, official checkpoint fixtures, and parity/benchmark measurements before those labels are allowed.