Repository navigation
WIP: DSV4 attention request-mode gate on native plan (item 27) - #630
Draft
inaniloquentee wants to merge 33 commits into
Draft
inaniloquentee wants to merge 33 commits into
inaniloquentee wants to merge 33 commits into
Conversation
Signed-off-by: fangfangssj <1135470306@qq.com>
Signed-off-by: Ziyi <ziyizhao0723@gmail.com>
docs: sync blog sidebar navigation
ws1-gtest-gpu and ws1-chain-gpu fail at "Configure runpodctl" before any test runs. They install releases/latest (v2.14.0 since 2026-09-10), whose deprecated `config --apiKey` aborts with `Config File ".runpod.yaml" Not Found` when it is the first runpodctl call on a fresh HOME. It only succeeds once an earlier call has created ~/.runpod/config.toml, which is why gpu-ci, whose install step happens to run `runpodctl version` first, got past the same command. Drop the config step in all three workflows. runpodctl v2 reads RUNPOD_API_KEY from the environment, and every step that runs ci/run_gpu_ci.sh already exports it, including the cleanup trap that calls `pod remove`. Verified for v2.9.0 inside `unshare -rn`, from a fresh HOME after `runpodctl version`: without the variable `pod list` fails locally with no_credentials, with RUNPOD_API_KEY=dummy it gets past the credential check to a network_error, and config.toml keeps `apikey = ''` throughout. v2.14.0 behaves the same. Pin the download to v2.9.0, the version gpu-ci run 31455127310 exercised end to end (pod create with sold-out fallback, pod id parsing, pod get polling, SSH, cleanup), and verify it with sha256sum -c against the runpodctl-linux-amd64 line of checksums_2.9.0_sha256.txt (06e6f54957db79d5cd9f1909a7f1d365076826751ba2f5df65d75dde43a64148), which matches GitHub's asset digest. Signed-off-by: Wenbo Ji <36562829+fusheng-ji@users.noreply.github.com>
fix(ci): pin runpodctl v2.9.0 and drop the deprecated config step (RUNPOD_API_KEY auth)
Signed-off-by: maxiaosong1124 <maxiaosong7890@outlook.com>
Signed-off-by: maxiaosong1124 <maxiaosong7890@outlook.com>
Signed-off-by: maxiaosong1124 <maxiaosong7890@outlook.com>
Signed-off-by: maxiaosong1124 <maxiaosong7890@outlook.com>
ci: remove obsolete RunPod WS1-chain-GPU workflow
Signed-off-by: maxiaosong1124 <maxiaosong7890@outlook.com>
Signed-off-by: maxiaosong1124 <maxiaosong7890@outlook.com>
Signed-off-by: maxiaosong1124 <maxiaosong7890@outlook.com>
Signed-off-by: maxiaosong1124 <maxiaosong7890@outlook.com>
ci: add RL-Kernel-specific automatic OCR review
Signed-off-by: maxiaosong1124 <maxiaosong7890@outlook.com>
Signed-off-by: maxiaosong1124 <maxiaosong7890@outlook.com>
Signed-off-by: lamentropetion <3051000145@qq.com>
docs(rocm): make the vLLM companion base reproducible from upstream
[Ascend] Fix deterministic attention backward compilation
…ned Graph records
…bi' into feat/dsv4-attention-runtime-bi
…into feat/dsv4-attention-runtime-bi
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
Comment |
Signed-off-by: ljj <ljj@users.noreply.github.com>
inaniloquentee
force-pushed
the
feat/dsv4-attention-runtime-bi
branch
from
October 29, 2026 11:56
d46ad78 to
b3c9bf6
Compare
This was referenced Oct 29, 2026
Collaborator
Author
|
Item-27 framework-integration gate checked on the
Before item 27 can leave draft: pin a compatible V4 vLLM/ROCm implementation and model checkpoint, wire the model call site to the shared plan, then validate prefill/decode/recompute, KV/O/LSE, Graph, and weight-version barriers in both frameworks. No V2 monkeypatch should be treated as a V4 integration. |
This branch has not been deployed
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.
Scope
Draft, partial item 27 of KLR #81 / RL-Kernel #514. Adds an opt-in request-mode gate around the existing native joint attention plan and autograd adapter. Tracks contiguous prefill/decode positions per request, enforces model/cache version transitions, and checks training/recompute Q, canonical KV, sink, logical selection, BF16 O and FP32 LSE byte-for-byte. Native operator failures cannot advance request state. No numerical GPU kernel has been copied or added.
Base and prerequisites
Started from latest
main8588158650aff58c9c1f527674de94bad06c3d10. This branch currently contains prerequisite #629 (including #628) and #626 (including #625/#624/#618), which are still open. Target isdsv4-rocm; it trails thatmainby 22 commits. Review this commit separately asd46ad78until prerequisites land.Verification
MI300X/gfx942 in the
ljjROCm container: 605 passed, 17 warnings across operator contracts and DeepSeek-V4 tests with pinned aiter forward/wrapper and Megatron backward sources; Ruff passed. New tests cover request sequencing, stale versions, provider failure, byte-preserving recompute under reordered rows, native Graph replay, and the native autograd path.Remaining before item 27 signoff
The current container exposes one GPU, and its model directory is empty. This PR must remain draft until the missing integration and acceptance evidence are supplied. It does not claim full model or two-node consistency.