diff options
| author | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-01 00:54:11 -0400 |
|---|---|---|
| committer | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-01 00:54:11 -0400 |
| commit | 5e3ada9c45d72688d1744f6a6191fb2bb4bbd319 (patch) | |
| tree | 429b1d8e7c489472062a1840f2fc1a6f2e152c79 /STATE-CURRENT.md | |
| parent | e25fc450abda40e54f4bfa7e59456a6ee8153a18 (diff) | |
| download | open-iov-5e3ada9c45d72688d1744f6a6191fb2bb4bbd319.tar.gz open-iov-5e3ada9c45d72688d1744f6a6191fb2bb4bbd319.zip | |
STATE-CURRENT: claim harness verified; rung-3 boot spec complete; FB-size decode identified
Diffstat (limited to 'STATE-CURRENT.md')
| -rw-r--r-- | STATE-CURRENT.md | 11 |
1 files changed, 9 insertions, 2 deletions
diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md index 3a3fd3d..dfd93cd 100644 --- a/STATE-CURRENT.md +++ b/STATE-CURRENT.md @@ -122,8 +122,15 @@ chain succeeds. image/version/signature sections identified) and the protected-region video-memory/boot layout is computed and logged - all without device writes. The unbind/rebind hazard is mitigated by the D0 power-domain lock, verified - over three supervised cycles; the next stage is the real GSP boot (secure - verification, booter, RISC-V start, resource-manager init). + over three supervised cycles; the ownership handoff is now also hardened + against the distribution driver's udev bind-event power-policy write, and a + reusable supervised claim-cycle harness exists + (`tools/guest-diag/phys_claim_cycle.sh`). The real-GSP-boot design is + complete: exact secure-verification/booter/RISC-V/RM-init sequence, boot + artifacts (booter/FMC/SEC2 BL bindata; VBIOS BIT FWSEC blob) and the real + FB-size decode (local-memory-range register; the BAR1-aperture approximation + is retired). Implementation starts with the real FB size and layout + self-checks, then secure verification, then the booter and RISC-V start. - Host stability: the host hang class observed on 2026-09-28 (kernel stack overflow in a channel snapshot path) is fixed and frame-audited; repeated VM load/attach/teardown cycles run without panics or pstore records. A |