M0: instrumentation and the per-epoch lost flag (no behaviour change) #1546

Open
opened 2026-11-15 06:01:14 +00:00 by sky_line · 0 comments
Owner

First step of the GPU-loss recovery epic. No behaviour change: a loss still ends the session as today (#135).

  • Make the device-lost flag per epoch (looked up by device / queue handle) instead of one process-wide latch that can never clear.
  • Classify every vkDeviceIsLost() and LLVulkanContext::instance() call site: current-epoch check vs a specific epoch.
  • Log where every thread is (main, present, texture prep, mesh decode, pipeline compile, NGX) when a loss is raised, to learn whether any thread is stuck inside a driver call during real losses.

Done when the build behaves exactly as before on a simulated and a real loss, the source checks cover the new flag, and the loss report shows each thread's state.

Part of #1545.

First step of the GPU-loss recovery epic. No behaviour change: a loss still ends the session as today (#135). - Make the device-lost flag per epoch (looked up by device / queue handle) instead of one process-wide latch that can never clear. - Classify every `vkDeviceIsLost()` and `LLVulkanContext::instance()` call site: current-epoch check vs a specific epoch. - Log where every thread is (main, present, texture prep, mesh decode, pipeline compile, NGX) when a loss is raised, to learn whether any thread is stuck inside a driver call during real losses. **Done when** the build behaves exactly as before on a simulated and a real loss, the source checks cover the new flag, and the loss report shows each thread's state. Part of #1545.
sky_line added this to the Slipstream project 2026-11-15 06:01:14 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sky_line/Slipstream#1546
No description provided.