diff options
Diffstat (limited to 'STATE-CURRENT.md')
| -rw-r--r-- | STATE-CURRENT.md | 25 |
1 files changed, 23 insertions, 2 deletions
diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md index be9cd48..733217f 100644 --- a/STATE-CURRENT.md +++ b/STATE-CURRENT.md @@ -1,6 +1,6 @@ # Open-IOV Current State -> **Snapshot: 2026-10-01 16:47.** This is a dated public status page, not live +> **Snapshot: 2026-10-01 18:47.** 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: @@ -57,7 +57,13 @@ meant to execute on the physical GPU. with a zero result and serve the full static-config reply (GPU name, 8 GiB FB, internal handles, BAR PDE bases, engine caps), and graceful shutdown works through the unload RPC. Each of cycles 4-13 released the device - cleanly with no reboot. | + cleanly with no reboot. Since 2026-10-01 17:24 the next rung has both code + and live results: a host resource-manager client creates memory and + channel-group objects on the booted server (nine allocations succeed) and is + blocked at channel allocation with an invalid-state result; one unsafe + channel variant hung the server task, so the fail-safe held the device and an + approved reboot restored it - the variant is removed from the tree. No + physical work has been submitted yet. | | Graphics (3D), video | ❌ | | Faults, multi-version, Windows, migration, multi-tenancy, performance | ❌ | @@ -69,6 +75,21 @@ chain succeeds. ## Right now (frontier) +- **Submission-rung bring-up (2026-10-01 17:24-18:47): the first real + resource-manager objects on the live GSP-RM.** A host resource-manager + client now talks to the booted server: nine memory allocations (system-memory + page-table registrations) and a channel-group object are created under the + server's own internal handles. The root-client allocation path is parked + after the server returned an invalid-client result, and channel allocation + is blocked at an invalid-state result; the next experiments are to allocate + and pass a virtual-address-space handle, or to vary the memory-descriptor + objects. One channel variant hung the server's resource-manager task; the + fail-safe held the device instead of handing it back in a wedged state, and + an approved reboot restored the distribution driver (~18:37). The unsafe + variant has been removed from the tree, and a decoded resource-manager log + dump now makes server-side failures readable. No work has been submitted to + the physical engine yet. Evidence: `backups/evidence-20261001-cycle14/` + through `...-cycle17/`. - **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: |