summaryrefslogtreecommitdiffstats
path: root/STATE-CURRENT.md
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-24 10:25:25 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-24 10:25:25 -0400
commit962f2171f31013791b6b02b305e091b849f67320 (patch)
tree01d0ef3243577e63989a28581ef6a7d2313a19a1 /STATE-CURRENT.md
parentb0819addd360b77626ca5c4a7830f8b2871ec576 (diff)
downloadopen-iov-962f2171f31013791b6b02b305e091b849f67320.tar.gz
open-iov-962f2171f31013791b6b02b305e091b849f67320.zip
STATE-CURRENT: refresh snapshot - 10 consecutive green physical-engine CUDA clients, launch p50 ~650ms, held-chain fix, variance root-caused, GL running, LG frame path proven
Diffstat (limited to 'STATE-CURRENT.md')
-rw-r--r--STATE-CURRENT.md25
1 files changed, 18 insertions, 7 deletions
diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md
index 27295df..d81de74 100644
--- a/STATE-CURRENT.md
+++ b/STATE-CURRENT.md
@@ -1,12 +1,23 @@
# Open-IOV Current State
-> **Snapshot: 2026-10-20 ~20:00 (two more fixes landed: the SWAP_RX cursor
-> and the pin-wins ledger divergence that cured a guest-kernel-corruption
-> panic; guest CUDA kernels green on fresh boots - `victory_mail`,
-> `victory_matmul` (first-run flake), transformer, `vector_add` (1M,
-> `bad=0`), `vecadd_loop` (100 launches); two guests with two emulated VRAM
-> sizes (512M + 1GiB) coexist live; frontier = the multi-pass content class
-> and the streams2 launch-order wait).**
+> **Snapshot: 2026-10-28 ~06:00 (physical-engine guest CUDA at 10
+> consecutive green clients on a fresh boot — `victory_mail`,
+> `victory_matmul`, `victory_saxpy`, `victory_strided`, `victory_math`,
+> `victory_reduce`, `victory_atomics`, `multikernel`, `vector_add` — with
+> launch p50 ~650 ms below the recorded 684 ms baseline; the held-chain
+> stall class root-caused and fixed (replay passes re-marking
+> `op_tr_pending`, re-arming a 3 s hold that stalled the copy channel); the
+> boot-to-boot variance root-caused (a per-client argument-base publication
+> race: green boots resolve each client's cudaMalloc base via the
+> FB-aperture directory walk, red boots return `none`/`rc=-2` on every
+> registered directory and the launch fails closed); the vidmem-window fill
+> decoder and the fail-closed defer-cap landed; GL now runs on the guest GPU
+> (VASpace construction and 3D-engine selection walls fixed; next wall = the
+> FBO class); the Looking Glass frame path is proven end-to-end (guest CUDA
+> render -> KVMFR ivshmem -> host PNG frame); two guests with 512M + 1GiB
+> emulated VRAM coexist at boot level; the 0.9.9 release-preview demo video
+> v1 is recorded. Frontier = the remaining boot variance + streams classes,
+> two-guest concurrent CUDA, GZDOOM (GL/Vulkan), Windows guests).**
> 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