diff options
Diffstat (limited to 'STATE-CURRENT.md')
| -rw-r--r-- | STATE-CURRENT.md | 16 |
1 files changed, 11 insertions, 5 deletions
diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md index 61f10f0..ed92566 100644 --- a/STATE-CURRENT.md +++ b/STATE-CURRENT.md @@ -1,6 +1,6 @@ # Open-IOV Current State -> **Snapshot: 2026-09-30 22:45.** This is a dated public status page, not live +> **Snapshot: 2026-09-30 23: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: @@ -101,11 +101,17 @@ chain succeeds. crashed the guest kernel (a NULL callback in interrupt context) before any emulation channel existed - guest-side and untriaged; treat no-watcher runs as a known risk. The host stays stable throughout. -- Execution backend (chosen; bring-up ladder drafted, not started): the - module will own the physical GPU and run its real GSP firmware as the - resource-manager server, so real work executes with an unmodified host - driver and no host daemon; see +- Execution backend (chosen; bring-up started): the module owns the physical + GPU and will run its real GSP firmware as the resource-manager server, so + real work executes with an unmodified host driver and no host daemon; see [`docs/03-architecture/08-physical-gpu-integration.md`](docs/03-architecture/08-physical-gpu-integration.md). + First bring-up steps verified live: a default-off claim path releases the + distribution driver from the device, binds the module, maps the BARs and + samples the falcon state, then releases and rebinds the distribution driver + (host driver still healthy); with the device owned, the matching GSP image is + fetched and validated (ELF64 RISC-V, loadable image/version/signature + sections identified) and held for the boot stage. The real boot (protected + region, secure verification, booter, RISC-V start) is the next stage. - 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. |