From 8c6bcb9a72c199368048d17e757814062b4765d1 Mon Sep 17 00:00:00 2001 From: Arthur Hanson Rasmusson Date: Thu, 1 Oct 2026 22:12:35 -0400 Subject: STATE-CURRENT: 22:12 check-back - guest-wiring rung opened (inert session API skeleton); PLAN A baseline re-verified 64/64 --- STATE-CURRENT.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) (limited to 'STATE-CURRENT.md') diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md index 9c417e3..15c167d 100644 --- a/STATE-CURRENT.md +++ b/STATE-CURRENT.md @@ -1,6 +1,6 @@ # Open-IOV Current State -> **Snapshot: 2026-10-01 21:05.** This is a dated public status page, not live +> **Snapshot: 2026-10-01 22: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: @@ -81,6 +81,19 @@ chain succeeds. ## Right now (frontier) +- **Guest-wiring rung has begun (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 + behaviour. In the same window the driver-API baseline was **re-verified green + on the current build**: a fresh VM cycle ran the smoke test end-to-end + (`ALL OK`, payload 64/64) with real releases (`faked=0 miss=0 stale=0`), so + the emulation front is intact ahead of the wiring work. The phased plan for + connecting the live session to the guest-facing path is + [`docs/03-architecture/11-physical-backend-guest-wiring.md`](docs/03-architecture/11-physical-backend-guest-wiring.md). + Post-single-VM-CUDA research notes (concurrent multi-VM virtual functions, + 3D acceleration, and a native-vs-guest performance program; and a host-side + acceleration feasibility study) were produced under `backups/` (untracked). - **Submission-rung milestone (2026-10-01 17:24-21:05): real work now executes on the physical engine.** The host resource-manager client allocated a virtual-address-space object with a committed page directory, a channel-group -- cgit v1.2.3