open-iov.git/userspace/cuda/570.144/docs/ANALYSIS-egl-engine-selection.md, branch masterOpen-IOV vGPU-IO: host-side GSP emulation for unmodified NVIDIA guest drivers
https://git.vgpu.io/open-iov.git/atom?h=master2026-10-23T15:15:53+00:00docs: ANALYSIS-egl-engine-selection - entry trace narrows the wall to glsi+0x33b80's state machine2026-10-23T15:15:53+00:00Arthur Hanson Rasmussonarthur@vgpu.io2026-10-23T15:15:53+00:00urn:sha1:00a03180413224dfc932c83a53fa2ccd145784ef
Batch-gdb entry trace (r543 boot): engine-init -> 1aba0 -> 22f30 (device
lookup, miss=0xee00002) / 2c360 (object lookup, miss=0xee00003) / 33b80
(device flags + state machine) -> 301b0 (state, 3a6f0 x7, 2ac10 x2) ->
EGL_BAD_ALLOC. All three lookups were entered, so the failure lands inside
33b80's state machine; the busy path (30ef2 in 30b20) sets bit 0x20 on the
per-engine state record and returns 0xee00001 once, and eglcore rejects the
engine without retry. 22f30 is called ~1300x (enumeration), so it is not a
lookup miss. Also records the inconclusive Xorg DMA/push-buffer test on a
boot that had a stalled client.
docs: ANALYSIS-egl-engine-selection - the EGL 3D-engine wall's failing chain (shipped-binary evidence)2026-10-23T12:08:41+00:00Arthur Hanson Rasmussonarthur@vgpu.io2026-10-23T12:08:41+00:00urn:sha1:a42e596308dc05e4b691ce219e27297872f7ccff
Records the eglcore->glsi chain that rejects the engine candidate
(0xee00001 out of the glsi engine-init), the ruled-out hypotheses (RM
controls answer NV_OK; the engine passes the walk's own filters; stable
under gdb no-ASLR) and the exact breakpoints/offsets for the next trace.