Skip to content

Start model-agnostic EXL3 SM121 kernel lab - #75

Merged
plotarmordev merged 5 commits into
MiaAI-Lab:mainfrom
Kristianaaron:feat/exl3-sm121-kernel-lab
Sep 15, 2026
Merged

plotarmordev merged 5 commits into
MiaAI-Lab:mainfrom
Kristianaaron:feat/exl3-sm121-kernel-lab

Conversation

@Kristianaaron

Copy link
Copy Markdown
Contributor

Summary

  • formalize the existing ExLlamaV3 EXL3/MCG packed ABI without inventing a new format
  • add deterministic K1-K8 pack/unpack and streaming matmul correctness oracles
  • add a direct packed EXL3 SM121 tactic sweep over compatible upstream kernel shapes and SM quotas
  • emit model-agnostic Atlas kernel benchmark receipts for arbitrary operator/K/N workloads
  • document the current production pin and an opt-in current-upstream QTIP/dp4a candidate build

Validation

  • python3 -m pytest tests/test_exl3_kernel_lab.py -q: 22 passed
  • runnable repository suite excluding the pre-existing optional chat-template dependency: 35 passed
  • CPU oracle K1-K8: 8/8 passed; worst max absolute error 1.07288361e-06

Hardware gate

This development host has no NVIDIA GPU. The PR intentionally makes no SM121 speed claim; the next step is to run the included isolated tactic sweep on a GB10/SM121 host and choose reconstruction, launch, or representation work from the measured bottleneck. The production ExLlamaV3 pin is unchanged.

@plotarmordev plotarmordev added triage/skip Community triage 2026-09-09: not recommended for a 2x GB10 TP=2 E3 deployment P3 Low urgency, experimental, stale, or needs more evidence merge-hold Do not merge until the stated maintainer dependency or hold is cleared. needs-final-review Prior audit is recorded; current-head review and merge disposition still need finalization. reviewed Our source review or technical verdict is recorded; not merge approval or runtime qualification. awaiting-test-evidence Reviewed; required exact-head correctness or performance evidence is still outstanding. and removed triage/skip Community triage 2026-09-09: not recommended for a 2x GB10 TP=2 E3 deployment needs-final-review Prior audit is recorded; current-head review and merge disposition still need finalization. labels Sep 9, 2026
@plotarmordev

Copy link
Copy Markdown
Collaborator

Review follow-up — bdc110e40c8f

The CPU oracle work and the explicit absence of an SM121 performance claim are acknowledged. We have not commissioned a hardware sweep, so awaiting-test-evidence is being removed.

This is a maintainer scope decision: whether the kernel lab belongs in the production image or should remain a separate development target. If we pursue it, the per-commit runtime stamp should also be moved after expensive build layers so changing that stamp does not unnecessarily invalidate their cache.

No new benchmark or rebase is requested from you while that decision is pending. The P3/merge hold denotes our deferral, not an unanswered testing request.

Unless explicitly noted above, this update is a source/discussion review, not a new live qualification run.

@plotarmordev plotarmordev removed the awaiting-test-evidence Reviewed; required exact-head correctness or performance evidence is still outstanding. label Sep 15, 2026
Keeps both sides of the README path table: main's TP3/TP4/NFS rows and the
kernel-lab rows added by this branch. No other integration change.
Maintainer decision on MiaAI-Lab#75: retain kernel_lab/, its CPU oracles/tests and
docs/exl3-sm121-kernel-lab.md in this PR as development-only work, and remove
every production Dockerfile addition from it. The ARG/ENV runtime stamp and
the kernel_lab COPY are gone, so the Dockerfile is byte-identical to main's
(pinned EXLLAMAV3_COMMIT build argument, compile/overlay layers and late
recipe-stamp conventions untouched).

README.md, kernel_lab/README.md and the engineering log now describe the lab
as a source checkout that the production Dockerfile neither copies nor
installs, drop the candidate-image build recipe and the in-image stamp claim,
and keep measured provenance fail-closed and declarative: --runtime-commit or
the clean checkout's Git identity, the environment override only when it is
exactly the loaded source, and a developer-provided backend must set its real
EXLLAMAV3_COMMIT before the metadata module is imported, since the pinned
fallback describes only the production pin. Historical author results stay
attributed and no speedup is claimed for the untimed SM121 sweep. No code
changes: kernel_lab/exl3/**, tests/test_exl3_kernel_lab.py are unchanged from
the author's head.

@plotarmordev plotarmordev left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

SIX exact-head approval: 289e365. Maintainer scope decision implemented in this same PR: kernel_lab, its CPU tests and docs are development-only; zero PR-attributable Dockerfile changes and no production launch hook. Independently reviewed all carried code and corrected developer provenance instructions. On this exact cumulative main-integrated head, /usr/bin/python3 ran 21 focused tests successfully, K1-K8 CPU oracle passed 8/8, and provenance smoke resolved the exact source SHA while refusing nonrepository and nonfull identity. PyTorch was absent; no CUDA/GPU inspection or measurement occurred. Complete publishing tree and pushed range scanned; author source branch/history preserved. No workflows/checks exist, not CI green. Runtime/backend identity remains a caller declaration, not binary attestation; historical CUDA claims remain author-attributed, and no SM121 speedup is claimed. Production-image scope hold is resolved; no hardware sweep was commissioned or required for development-only inclusion.

@plotarmordev
plotarmordev merged commit a9bbbad into MiaAI-Lab:main Sep 15, 2026
@plotarmordev plotarmordev removed the merge-hold Do not merge until the stated maintainer dependency or hold is cleared. label Sep 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

P3 Low urgency, experimental, stale, or needs more evidence reviewed Our source review or technical verdict is recorded; not merge approval or runtime qualification.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants