M0: instrumentation and the per-epoch lost flag (no behaviour change) #1546
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#1546
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
First step of the GPU-loss recovery epic. No behaviour change: a loss still ends the session as today (#135).
vkDeviceIsLost()andLLVulkanContext::instance()call site: current-epoch check vs a specific epoch.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.