GPU passes: result points, where in the waited-for submissions the results the game's wait needs are done on the GPU, and how much earlier the wait could end.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Tobim6
2026-11-12 16:23:07 +01:00
parent 306de50589
commit aa1045d411
4 changed files with 115 additions and 0 deletions

View File

@@ -67,6 +67,10 @@ typedef struct { uint64_t addr, size; int back; } Range; // back: written into
// for the newest such submission). Write-backs of the mirrors note it in vk_memory.c; the lazily written ones fetch on
// the CPU's first access.
static volatile int32_t ex_results; // VK_RES_* bits
void vk_exec_note_results(int kind) {
__atomic_fetch_or(&ex_results, kind, __ATOMIC_RELAXED);
vk_gpu_passes_result(kind); // NX2NAVI_GPU_PASSES: where in the submission it is done
}
int vk_exec_take_results(void) { return __atomic_exchange_n(&ex_results, 0, __ATOMIC_RELAXED); }
static void guest_written_cb(void *arg) {