mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-20 21:09:57 -04:00
Keep an optional history of GPU address ranges, so the report of a lost graphics device can name what held the faulting address.
After a lost device the driver's fault report gives an address and nothing says what was there. With va_report = 1 (NX2NAVI_VA_REPORT, off by default) the game keeps every address range the driver binds to a buffer or image and every range it unbinds (VK_EXT_device_address_binding_report, runtime/vk_vaddr.c). The report of a lost device then names the ranges that covered each faulting page, or the nearest ones when none did, and vaddr-history.txt beside the log holds the whole history, also when the driver gives no fault report. With 2 the call stack behind each range of 1 MiB or more is kept too. A player sees nothing of this unless the setting is on: without it no extension is enabled and no callback runs. From pull request #349. Its second part, which stops a frame dump from turning on mesh query statistics, is left out: it changes what a dump writes for everyone who uses one. Built for Windows; no device was lost to try it. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
@@ -82,6 +82,15 @@ int vk_selftest(void); // 0 on success
|
||||
// process, after the GPU breadcrumbs (vk_crumbs_report). Any other result returns at once.
|
||||
void vk_device_fault_report(VkResult r);
|
||||
|
||||
// ---- GPU address history (vk_vaddr.c, NX2NAVI_VA_REPORT=1, 2 with call stacks): VK_EXT_device_address_binding_report's
|
||||
// reports, kept so vk_device_fault_report can name the objects that held a faulting address.
|
||||
int vk_vaddr_wanted(void);
|
||||
void vk_vaddr_start(VkInstance instance); // create_instance, after vkCreateInstance
|
||||
void vk_vaddr_device(int supported); // create_device: the driver reports address bindings
|
||||
void vk_vaddr_fault(uint64_t addr, uint64_t precision); // logs the reports whose range covered addr's page
|
||||
void vk_vaddr_dump(void); // the whole history to vaddr-history.txt beside the log
|
||||
void vk_vaddr_stop(VkInstance instance); // before vkDestroyInstance
|
||||
|
||||
// ---- GPU breadcrumbs (vk_crumbs.c): with VK_AMD_buffer_marker, each crumb has the GPU write its code into host memory
|
||||
// twice, when the command processor reaches it and when all work before it has finished. After a lost device the two
|
||||
// codes bracket the work that hung. Without the extension every call returns at once.
|
||||
|
||||
Reference in New Issue
Block a user