STATE-CURRENT: physical GSP-RM completes initialization and serves the static-config RPC

1 files changed, 25 insertions, 1 deletions

diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md
index 2f11b57..20a0120 100644
--- a/STATE-CURRENT.md
+++ b/STATE-CURRENT.md
@@ -1,6 +1,6 @@
 # Open-IOV Current State
 
-> **Snapshot: 2026-10-01 15:47.** This is a dated public status page, not live
+> **Snapshot: 2026-10-01 16:45.** This is a dated public status page, not live
 > state; it is refreshed on every progress check. Live working notes are
 > maintained outside this repository; the public known-knowns/unknowns document
 > is authoritative here:
@@ -62,6 +62,30 @@ chain succeeds.
 
 ## Right now (frontier)
 
+- **Physical-backend milestone (2026-10-01 16:45): the host-owned GSP-RM
+  completes initialization on the real TU104 and serves the static-config
+  RPC.** Three supervised cycles, no reboot, clean release each time:
+  1. the resource-manager log ring is now registered correctly (its libos
+     init-argument id was malformed), which made the server's previously
+     invisible first error readable: a device-name lookup failing because the
+     server's chip device-id was zero (cycle 11);
+  2. the pre-boot system-information payload now carries the raw PCI
+     config-space identity dwords (`device<<16|vendor`) instead of unpacked
+     16-bit fields, and the static-config RPC now declares the full reply
+     payload; the server then reports init-done with `rpc_result=0`
+     (cycle 12);
+  3. the static-config RPC returns the full 1656-byte configuration - GPU
+     name `NVIDIA GeForce RTX 2080 Super with Max-Q Design`, short `TU104-B`,
+     8 GiB FB, internal client/device/subdevice handles, BAR PDE bases,
+     engine caps - and shutdown runs through the unload RPC (GSP-RM processor
+     suspended in ~220 ms, handoff bits complete) with WPR2 down and the
+     distribution driver rebound (cycle 13).
+
+  The physical backend is now a live, queryable GSP-RM: the host can boot it,
+  send RM RPCs and receive full replies, and shut it down gracefully. The
+  next rung is to drive the guest-facing emulation from this backend.
+  Evidence: `backups/evidence-20261001-cycle11/`, `...-cycle12/`,
+  `...-cycle13/`.
 - **Driver-API baseline re-verified green on the current build** (2026-10-01
   14:20): the smoke test passes end-to-end (`ALL OK`, payload 64/64) with
   real releases (`faked=0`, `miss=0`, `stale=0`); the source-level root-cause