From 4a2cf8292ad37767de22a26e7e35d0a8a06edad3 Mon Sep 17 00:00:00 2001 From: Arthur Hanson Rasmusson Date: Mon, 9 Nov 2026 19:08:20 -0500 Subject: wiki: 2026-11-09 evening refresh 2 - forced GLX reaches glcore; windowed GL waits on kernel kick completion Refresh STATE-CURRENT, the Main Page and the status/frontier pages: with SDL_VIDEO_X11_FORCE_EGL=0 the windowed GL path selects libnvidia-glcore, but the minimal glxgears hangs in the glcore kick wait (poll on the per-slot /dev/nvidia-modeset fd) while the host completes the beef notifier memory. The X DDX get-word/notifier completion, the DDX 4 GB sysmem footprint and physical dispatch of the GL draws remain. Published to open-iov.org. --- wiki/FAQ.md | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) (limited to 'wiki/FAQ.md') diff --git a/wiki/FAQ.md b/wiki/FAQ.md index 57f8218..5025175 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 @ e342bd0f`. +Status: 2026-11-09, tree `master @ 21e0d611`. ## Project and positioning @@ -40,14 +40,17 @@ 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 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 +the direct GL client's GR and CE channels submit and retire, and forcing GLX +(`SDL_VIDEO_X11_FORCE_EGL=0`) selects `libnvidia-glcore`. The minimal +windowed `glxgears` then hangs in the glcore kick wait: the client polls its +per-slot `/dev/nvidia-modeset` fd and the guest kernel never signals the +event, even though the host completes the beef notifier memory. 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: kernel-visible present completion, 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?** -- cgit v1.2.3