summaryrefslogtreecommitdiffstats
path: root/STATE-CURRENT.md
Commit message (Collapse)AuthorAge
* STATE-CURRENT: 23:12 check-back - guest-wiring P1 lifecycle landed and ↵Arthur Hanson Rasmusson14 days
| | | | exercised (fail-open); async boot FWSEC failure and a release-path freeze recurrence noted
* docs: record host VF acceleration as a deferred future goalArthur Hanson Rasmusson14 days
|
* STATE-CURRENT: 22:12 check-back - guest-wiring rung opened (inert session ↵Arthur Hanson Rasmusson14 days
| | | | API skeleton); PLAN A baseline re-verified 64/64
* STATE-CURRENT + docs: first real copy executed by the physical CE; add the ↵Arthur Hanson Rasmusson14 days
| | | | | | | | | | | | | | physical-backend guest-wiring design - STATE-CURRENT snapshot 2026-10-01 21:05: the host RM-client ladder now allocates VAS+PDB+TSG+channel and executes a real 4 KiB VA-mode CE copy (semaphore released, dst==src) on the physical engine; next is wiring the live session into the guest-facing mdev/vfio path. - docs/03-architecture/11-physical-backend-guest-wiring.md: phased design (P0-P6) for bridging the physical backend into the guest-facing emulation, with the seam table, lifecycle changes and static-config flow. - docs/README.md: reading order updated for the new document; execution status refreshed.
* STATE-CURRENT: 20:12 check-back - first real GPFIFO work submitted to the ↵Arthur Hanson Rasmusson14 days
| | | | physical engine; channel now allocates; engine did not execute the block
* STATE-CURRENT: 19:12 check-back - host RM client allocates a VAS on the live ↵Arthur Hanson Rasmusson14 days
| | | | GSP-RM; wall moved to the address-space page-directory setup; clean release
* STATE-CURRENT: 18:47 check-back - first RM objects on the live GSP-RM; ↵Arthur Hanson Rasmusson14 days
| | | | channel allocation blocked; unsafe variant removed after fail-safe reboot
* STATE-CURRENT: 16:47 check-back - ladder row updated for the GSP-RM init ↵Arthur Hanson Rasmusson2026-10-01
| | | | milestone (log-ring and identity fixes)
* STATE-CURRENT: physical GSP-RM completes initialization and serves the ↵Arthur Hanson Rasmusson2026-10-01
| | | | static-config RPC
* STATE-CURRENT: 15:47 check-back - source campaign closes host-side inputs; ↵Arthur Hanson Rasmusson2026-10-01
| | | | PMU-provisioned chip identity is the one hard dependency
* STATE-CURRENT: cycles 4-10 - pre-boot RPCs/registry/timer/chipset landed; RM ↵Arthur Hanson Rasmusson2026-10-01
| | | | init wall narrowed to static-config collection
* STATE-CURRENT: physical GSP-RM init root-caused to devid validation; cycle 8 ↵Arthur Hanson Rasmusson2026-10-01
| | | | under test
* STATE-CURRENT: 14:07 check-back - 0x59 root-caused (missing pre-boot init ↵Arthur Hanson Rasmusson2026-10-01
| | | | handshake); error journal collapsed 851->4; cycles 4-7 release clean
* STATE-CURRENT: 12:12 check-back - cycles 2-3 ran the real GSP-RM sequencer; ↵Arthur Hanson Rasmusson2026-10-01
| | | | RM init fails 0x59; clean release without reboot; NOCAT capture next
* STATE-CURRENT: cycles 2-3 results - clean release without reboot; RM init ↵Arthur Hanson Rasmusson2026-10-01
| | | | failure 0x59 under diagnosis
* STATE-CURRENT: stage 3e parser fix after the live GSP-RM sequencer request; ↵Arthur Hanson Rasmusson2026-10-01
| | | | next cycle prepared
* docs: record next-cycle readiness for the physical GSP bootArthur Hanson Rasmusson2026-10-01
| | | | STATE-CURRENT and the integration page reflect the implemented sequencer, clean-shutdown RPC and static-info probe awaiting the next supervised live cycle.
* STATE-CURRENT: 10:08 check-back snapshot (first real GSP boot recorded; ↵Arthur Hanson Rasmusson2026-10-01
| | | | sequencer executor next)
* docs: record the first real GSP boot and the live GSP-RM sessionArthur Hanson Rasmusson2026-10-01
| | | | STATE-CURRENT and the architecture docs now describe the observed order (FWSEC -> Booter Load -> RISC-V active -> event 0x1002 run-sequencer -> 0x1001 init-done), the four-handoff-bit clean-release constraint, and the --boot/--keep harness contract.
* STATE-CURRENT: recovery complete (approved reboot restored GPU); ↵Arthur Hanson Rasmusson2026-10-01
| | | | secure-verification-only retired; full boot lifecycle next
* STATE-CURRENT: FWSEC carve milestone; fail-safe teardown limit; approved ↵Arthur Hanson Rasmusson2026-10-01
| | | | reboot for restoration
* STATE-CURRENT: live secure-verification succeeded (WPR2 up); fail-safe holds ↵Arthur Hanson Rasmusson2026-10-01
| | | | device pending rescue
* STATE-CURRENT: supervised D0 claim mitigation verified (3/3); FB 8 GiB; ↵Arthur Hanson Rasmusson2026-10-01
| | | | FWSEC dry-run stage
* STATE-CURRENT: 07:12 check-back snapshot (backend hardening/read-only ↵Arthur Hanson Rasmusson2026-10-01
| | | | dry-run stage before live boot)
* STATE-CURRENT: PLAN B claim path proven safe 3/3; real FB size 8 GiB; ↵Arthur Hanson Rasmusson2026-10-01
| | | | secure-verification stage coded (build-only)
* STATE-CURRENT: claim harness verified; rung-3 boot spec complete; FB-size ↵Arthur Hanson Rasmusson2026-10-01
| | | | decode identified
* STATE-CURRENT: D0 lock verified 3/3 supervised claim/release cycles; real ↵Arthur Hanson Rasmusson2026-10-01
| | | | GSP boot is next
* STATE-CURRENT: power-domain lock implemented behind the hazard gate; ↵Arthur Hanson Rasmusson2026-10-01
| | | | snapshot refreshed
* STATE-CURRENT: cdt2 baseline re-verified; second freeze class mechanism and ↵Arthur Hanson Rasmusson2026-10-01
| | | | power-domain mitigation recorded
* STATE-CURRENT: execution backend hazard-gated after freeze root-cause; ↵Arthur Hanson Rasmusson2026-09-30
| | | | bring-up snapshot refreshed
* STATE-CURRENT: root-cause the second freeze class (claim unbind) and its ↵Arthur Hanson Rasmusson2026-09-30
| | | | hazard gate
* STATE-CURRENT: execution-backend bring-up started (claim + GSP firmware ↵Arthur Hanson Rasmusson2026-09-30
| | | | verified); freeze-class watch note
* docs: execution-backend bring-up staged - ownership and firmware staging ↵Arthur Hanson Rasmusson2026-09-30
| | | | verified, real boot next
* STATE-CURRENT: cdt2 64/64 rerun verified; execution backend bring-up ladder ↵Arthur Hanson Rasmusson2026-09-30
| | | | drafted
* STATE-CURRENT: real-release rc=0 chain reached; execution backend is the ↵Arthur Hanson Rasmusson2026-09-30
| | | | | | | | | | | | frontier - the per-push 8 s stall was pump bookkeeping (release-seen keyed on the unchanged tracker-semaphore VA; rewind replays returning to the CE grace path) - fixed; real-release init now completes in ~1 min - the content rescue now parses the real method encoding, so NON_INC-headed pushes validate and their releases land - the queued launch's module image reaches the emulated vidmem; execution on real hardware (docs/03-architecture/08 backend) is the next project
* STATE-CURRENT: no-pin release delivery committed; real-release init reaching ↵Arthur Hanson Rasmusson2026-09-30
| | | | | | | | device count - 6ec799c delivers UVM tracking releases without host-side pins - one real-release no-watcher cycle reached cudaGetDeviceCount success - cycles continue; execution backend remains the gating item
* STATE-CURRENT: no-watcher cycles iterating (module rebuilt from the ↵Arthur Hanson Rasmusson2026-09-30
| | | | | | | in-flight edit) - three real-release cycles without kprobes/watchers; no textual result yet - frontier unchanged: real-release runtime init and the execution backend
* STATE-CURRENT: activity resumed - no-watcher real-release runtime cyclesArthur Hanson Rasmusson2026-09-30
| | | | | | - fresh module per cycle without kprobes/watchers; early observation: a compute-channel entry stalls with a failure notifier - frontier unchanged: real-release runtime init and the execution backend
* STATE-CURRENT: runtime client reaches kernel launch; execution backend is ↵Arthur Hanson Rasmusson2026-09-30
| | | | | | | | the next wall - runtime init rc=0 (cudaGetDeviceCount/SetDevice/alloc/HtoD/launch accepted) - fixed the legacy clock-domain probe replies that blocked runtime init - next: real-release runtime init and physical-GPU execution of queued work
* STATE-CURRENT: PD writes proven live; runtime client past registration; ↵Arthur Hanson Rasmusson2026-09-30
| | | | | | | | canonical reply fix - page-directory entry writes captured and validated; 64/64 baseline stays - vectorAdd client now fails after registration in libcuda (rc=3), no kernel error - BAR-info canonical reply-size bug fixed; one cache mismatch remains
* STATE-CURRENT: quiet logging landed; baseline verified twice; PD-capture ↵Arthur Hanson Rasmusson2026-09-30
| | | | | | | | task next - dmesg diagnostics gated behind default-off sema_dbg; 64/64 with a 520-line log - staging buffer kept resolvable via streamed pins; PD-entry capture remains - note the guest-side kernel fault observed in serial
* STATE-CURRENT: payload roundtrip 64/64 restored by the page-table ↵Arthur Hanson Rasmusson2026-09-30
| | | | | | | | publication capture - the device-to-host destination now resolves; baseline green again in live runs - frontier/active-work notes updated: land the capture fix, then the runtime vectorAdd client
* STATE-CURRENT: baseline regression (DtoH destination translation) and the ↵Arthur Hanson Rasmusson2026-09-30
| | | | targeted-fallback/retry work
* docs: retire the 2026-09-21 STATE.md snapshotArthur Hanson Rasmusson2026-09-30
| | | | | | | - remove the superseded flat state page; current state lives in STATE-CURRENT.md and the docs tree - update the historical-material note in docs/README and the STATE-CURRENT header/see-also references
* STATE-CURRENT: runtime bring-up started; runtime buffer translations are the ↵Arthur Hanson Rasmusson2026-09-30
| | | | | | | | | wall - harness runs nvidia-smi and a static-runtime vectorAdd-style client - page-table walk succeeds at scale; larger runtime buffers still fail translation (host copies report missing entries) - frontier/active-work notes updated
* STATE-CURRENT: full driver-API smoke test passes with payload 64/64Arthur Hanson Rasmusson2026-09-30
| | | | | | | - milestone: cuCtxCreate through cuCtxDestroy with correct data roundtrip - GMMU walk decode fixed (real entry encoding); DtoH copy-engine-on-compute allowed for trusted injected pushes - ladder/diagrams/rails updated; next rung is real CUDA workloads
* STATE-CURRENT: payload path found (compute-class inline DMA); page-table ↵Arthur Hanson Rasmusson2026-09-30
| | | | | | | | | walk is the wall - smoke test ends ALL OK; data roundtrip pending the GPU-VA walk - HtoD identified as a GRCE inline-data DMA and decoded; destination translation is the remaining blocker - frontier/rail refreshed
* sema-svc: run CE work before its release, grace unreadable CE entries, ↵Arthur Hanson Rasmusson2026-09-30
| | | | | | | | | | | | | | | | | | | payload-pattern audit - CE LAUNCH_DMA releases are now applied after the push's collected work runs: the client reads copied data as soon as it observes the release, so release-first let cuMemcpyDtoH observe a copy that had not executed. - Unreadable CE entries stay pending for a grace window (sema_ce_grace_ms, default 8s) before the release fallback consumes them, so a translation that lands within a service pass lets the push be decoded and its work executed instead of being dropped. - sema_copy_pat matches an 8-byte value against every copy's src/dst first word and scans decoded pushes for it, naming the submission that carries a known payload regardless of size/encoding. - sema-dma-skip logs transfer-shaped launches that collect no op; op log lines carry the channel handle; LAUNCH_DMA inventory follows OPS_LOG. - A real release application now records the release VA, so decoded pushes no longer trigger a spurious fake release.
* STATE-CURRENT: cuCtxCreate 999 root-caused and fixed; UVM runtime progressArthur Hanson Rasmusson2026-09-30
| | | | | | | | - GR-info indices 7/9/0x17/0x22 were zero in the emulation (shader-pipe sub-count among them); filling real-device values clears the previously fatal context check - client now runs inside UVM for minutes instead of failing in seconds - next wall: push-data operand translation (fix in); frontier notes updated
* docs: refresh current-state snapshot (20/20 GR releases land; failure not a ↵Arthur Hanson Rasmusson2026-09-30
| | | | UVM wait)