wiki: 2026-11-10 afternoon refresh - first real GPU readback; direct-GL/window walls

Refresh STATE-CURRENT, the Main Page and the status/frontier pages: the DDX
3D replay executes and a guest pbuffer glClear+glReadPixels returns a red
pixel (ff0000ff); the RM write-lock holder (Xorg in the DDX scrub wait) is
fixed in df6e71bb. The direct-GL client channel still emits only setup/notify
kicks (ops_runs=0), a window draw wedges X, and X startup/RM stability plus
the DDX 4 GB sysmem allocation remain. Published to open-iov.org.

1 files changed, 1 insertions, 1 deletions

diff --git a/tools/site/pages/Main-Page.wiki b/tools/site/pages/Main-Page.wiki
index c29e5c1..f3fb52a 100644
--- a/tools/site/pages/Main-Page.wiki
+++ b/tools/site/pages/Main-Page.wiki
@@ -36,7 +36,7 @@ The only new component is one host kernel module (<code>vgsp.ko</code>), which i
 |-
 | Display and KMS (nvidia-modeset/NvKms, /dev/dri, X) || Working — the emulated display engine serves the modeset push buffers and notifier completion; NvKms registers, X settles and glxinfo reports OpenGL 4.6.0 with direct rendering
 |-
-| 3D graphics: Xorg + OpenGL, Vulkan || In progress — the display/KMS and GL stacks run, the direct GL client's GR/CE channels submit and retire, the GSP event-IRQ fix completes swaps, X is reliable, and the guest's real GL draws now forward and execute on the physical GPU; the 2D path is green. The draw still writes 0 pixels: the beef GR ring resolution, the fixed-CB image's zero MVP block and the render-target bind are the current frontier — see [[Graphics Execution]], [[OpenGL]], [[Vulkan]]
+| 3D graphics: Xorg + OpenGL, Vulkan || In progress — the display/KMS and GL stacks run, the 2D path is green, the DDX 3D replay executes, and the first real GPU readback is proven (pbuffer red pixel). The direct-GL client channel still emits only setup/notify kicks and a window draw wedges X, so direct-GL draw capture and the window/screen present are the current frontier — see [[Graphics Execution]], [[OpenGL]], [[Vulkan]]
 |-
 | Windows guests, multi-tenancy, migration, performance || Not yet — multiple mediated devices (different emulated VRAM sizes) and multiple guests already coexist; per-guest execution isolation is in progress
 |}