Take out the GPU address history of a lost device's report.

The author of the pull request it was ported from closed that request on 2026-11-11 with the words that they give no
permission to use its code. The history (NX2NAVI_VA_REPORT, runtime/vk_vaddr.c, the stack walk it used and its notes
in the docs and the example settings) goes; the lost device's report keeps the breadcrumbs, the pass marks, the video
memory and the driver's fault information.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-11 08:18:55 -05:00
parent 3d394dd84e
commit bdc67cebfc
9 changed files with 5 additions and 69 deletions

View File

@@ -323,13 +323,6 @@ Before a commit:
`git config core.hooksPath .githooks` runs it before each local commit.
- `build\<ver>\nx2navi.exe --selftest`: layout, dispatch table and host-function registry, without game files.
GPU page faults: `NX2NAVI_VA_REPORT=1` keeps the driver's GPU address bind/unbind reports
(VK_EXT_device_address_binding_report, `runtime/vk_vaddr.c`); `=2` also keeps the host call stack of ranges of 1 MiB
or more. After a lost device, the log names the reports whose range covered each faulting page, or the nearest ranges
when none did, and `vaddr-history.txt` beside the log holds the whole history. Stack frames are module offsets: add
the executable's load address (the link map's base) before looking them up in `ocarina.map`. Each bind and unbind
costs a callback, and `=2`'s stack walks enough to hide a timing-dependent fault.
A change to the in-game menu's look (`runtime/ui/menu_skin.cpp`, `option_rows.cpp`, `perf_panel.cpp`) can be looked at
without game files: `python tools/menu_preview.py` builds the menu's own drawing code with the host's clang++ and
writes the Screen tab, the full performance overlay and the boot screen to `build/menu-preview/` (`menu.png`,