diff options
Diffstat (limited to 'wiki/FAQ.md')
| -rw-r--r-- | wiki/FAQ.md | 23 |
1 files changed, 11 insertions, 12 deletions
diff --git a/wiki/FAQ.md b/wiki/FAQ.md index 57782e7..e4361a6 100644 --- a/wiki/FAQ.md +++ b/wiki/FAQ.md @@ -5,7 +5,7 @@ > [`../docs/09-reference/glossary-and-faq.md`](../docs/09-reference/glossary-and-faq.md); > the docs tree wins on disagreement. -Status: 2026-11-09, tree `master @ bb802909`. +Status: 2026-11-09, tree `master @ df6e71bb`. ## Project and positioning @@ -40,17 +40,16 @@ progress). This is the project's known status, not a misconfiguration — see Partially, and it is an active frontier. The display/KMS stack and the X server now run on the emulated vGPU with the stock driver: nvidia-modeset/NvKms registers (`/dev/dri`), `glxinfo` reports OpenGL 4.6.0 with direct rendering, -the direct GL client's GR and CE channels submit and retire, and the GSP -event-IRQ fix completes swaps. X is green on attempt 1, the guest's **real GL -draws forward and execute on the physical GPU** (`work_gr backend_ok=5-7`, -`backend_timeout=0`), and the 2D path is green end-to-end, but the frames are -black: the replayed draw writes 0 pages because the beef GR ring does not -resolve deterministically, the fixed-CB image's `0x80` MVP block is zero, and -the render-target bind is unconfirmed. The guest Vulkan pipeline runs end to -end (device → command buffer → fence → readback, frames black). These three -plus the DDX's 4 GB sysmem allocation (12 GB guest workaround) are the -current gates — see [`OpenGL.md`](OpenGL.md), [`Vulkan.md`](Vulkan.md) and -[`Graphics-Execution.md`](Graphics-Execution.md). +the 2D path is green and the DDX 3D replay executes; the **first real GPU +readback** landed (a pbuffer `glClear(red)+glReadPixels` probe returns +`pixel=ff0000ff`). The RM write-lock holder (Xorg in the DDX vidheap scrub +wait) was identified and fixed (`df6e71bb`). The guest Vulkan pipeline runs +end to end (device → command buffer → fence → readback, frames black). Screen +pixels are still the wall: the direct-GL client channel `0xbfef0002` emits +only setup/notify kicks (`ops_runs=0`), a synchronous window draw wedges X, +and X startup/RM degradation (`0x51`) plus the DDX's 4 GB sysmem allocation +(12 GB guest workaround) remain — see [`OpenGL.md`](OpenGL.md), +[`Vulkan.md`](Vulkan.md) and [`Graphics-Execution.md`](Graphics-Execution.md). **How fast is it?** No published numbers yet. Kernel launches execute on the physical engine; |