diff options
| -rw-r--r-- | STATE-CURRENT.md | 19 |
1 files changed, 16 insertions, 3 deletions
diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md index 261269e..fd737c7 100644 --- a/STATE-CURRENT.md +++ b/STATE-CURRENT.md @@ -1,6 +1,6 @@ # Open-IOV Current State -> **Snapshot: 2026-10-01 22:12.** This is a dated public status page, not live +> **Snapshot: 2026-10-01 23:12.** 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: @@ -69,7 +69,7 @@ meant to execute on the physical GPU. and destination equal to source. Every cycle released the device cleanly with no reboot; the next rung is wiring the live physical session into the guest-facing mdev/vfio path - ([`docs/03-architecture/11-physical-backend-guest-wiring.md`](docs/03-architecture/11-physical-backend-guest-wiring.md)). | + ([`docs/03-architecture/11-physical-backend-guest-wiring.md`](docs/03-architecture/11-physical-backend-guest-wiring.md)). The guest-wiring rung then advanced: an inert backend-session API was added, and the mediated-device-owned lifecycle (P1, see the frontier section) was implemented and exercised - deferring the physical claim/boot to the first device create, releasing it on the last remove, with fail-open behaviour. | | Graphics (3D), video | ❌ | | Faults, multi-version, Windows, migration, multi-tenancy, performance | ❌ | @@ -81,7 +81,20 @@ chain succeeds. ## Right now (frontier) -- **Guest-wiring rung has begun (2026-10-01 22:00): the first backend-session +- **Guest-wiring lifecycle (P1) implemented and exercised (2026-10-01 22:22).** + A module parameter selects a lifecycle where the physical-GPU claim and boot + are deferred to the first mediated device create and released on the last + remove, run asynchronously and **fail-open**: if the backend boot fails the + device keeps serving the emulation path. An acceptance cycle verified the + deferred claim, the fail-open behaviour (the boot failed at the secure + verification stage, yet the smoke test still passed `ALL OK` payload 64/64 + while the backend stayed off), and the release on remove. Two follow-ups + opened: the asynchronous boot failed where the supervised cycles had + succeeded, and the release/rebind was followed by a host power-management + freeze of the known kind (the GPU power-gating hazard), which needed an + unplanned reboot; the release path must keep the board powered through the + driver resume. No guest work is forwarded to the physical engine yet. +- **Guest-wiring rung opened (2026-10-01 22:00): the first backend-session API code is in the tree, inert.** A skeleton that exposes the live physical session to the device layer (session request entry points plus a static-info snapshot helper) was added behind the existing gates and does not yet alter |