diff options
| author | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-11-09 19:05:16 -0500 |
|---|---|---|
| committer | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-11-09 19:05:16 -0500 |
| commit | 21e0d611b5efbdcf6a14520c3294d6a78bb32220 (patch) | |
| tree | 84f36e306b7b1a7b551075f578245765949b42e2 /wiki/FAQ.md | |
| parent | e342bd0f6d813d246c698d19a5828e7f8d817183 (diff) | |
| download | open-iov-21e0d611b5efbdcf6a14520c3294d6a78bb32220.tar.gz open-iov-21e0d611b5efbdcf6a14520c3294d6a78bb32220.zip | |
wiki: 2026-11-09 evening refresh - X DDX waits fixed; GZDoom reaches MAP01 on llvmpipe
Refresh Project Status, Graphics Execution, OpenGL, Execution Frontier,
Execution Plane, Physical GPU Backend, Host Module, System Overview,
Project Goals, Project Plan and the FAQ, plus STATE-CURRENT and the Main
Page: the X DDX waits (class-aware display arm, 0x8000->0 notification
completion, decoded GL release) are fixed; GZDoom reaches MAP01 on Mesa
llvmpipe; the NVIDIA renderer path, the DDX get-word/notifier completion,
the DDX 4 GB sysmem footprint and physical dispatch of the GL draws are
the pixel walls. Published to open-iov.org.
Diffstat (limited to 'wiki/FAQ.md')
| -rw-r--r-- | wiki/FAQ.md | 15 |
1 files changed, 9 insertions, 6 deletions
diff --git a/wiki/FAQ.md b/wiki/FAQ.md index 4fa79aa..57f8218 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 @ 4acc81e8`. +Status: 2026-11-09, tree `master @ e342bd0f`. ## Project and positioning @@ -40,11 +40,14 @@ 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, -GZDoom obtains a real GL context, and the direct GL client's GR and CE channels -submit and retire; the guest Vulkan pipeline runs end to end (device → command -buffer → fence → readback). Rendered (non-black) frames are the remaining wall -— the X GLX context-creation completion and the client kick-slot word are the -current gates — see [`OpenGL.md`](OpenGL.md), [`Vulkan.md`](Vulkan.md) and +the direct GL client's GR and CE channels submit and retire, and GZDoom +reaches renderer startup and `MAP01` — but currently on Mesa llvmpipe. The +guest Vulkan pipeline runs end to end (device → command buffer → fence → +readback, frames black). Rendered (non-black) frames through the NVIDIA path +are the remaining wall: the NVIDIA Vulkan ICD/forced-GLX renderer path, the X +DDX get-word/notifier completion, the DDX's 4 GB sysmem allocation (12 GB +guest workaround) and physical dispatch of the GL draws are the current gates +— see [`OpenGL.md`](OpenGL.md), [`Vulkan.md`](Vulkan.md) and [`Graphics-Execution.md`](Graphics-Execution.md). **How fast is it?** |