summaryrefslogtreecommitdiffstats
path: root/wiki/open-iov.org/index.php?title=File:Virgl.png&action=edit.html
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-23 18:40:12 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-23 18:40:12 -0400
commit41f6bf1a07fbf33036d31fe64c98d64cfe621e67 (patch)
treed748c222cb7170ef165f100cb9658b1b8e78f8a2 /wiki/open-iov.org/index.php?title=File:Virgl.png&action=edit.html
parent4f28cbed07a20b290891e7325a07072326c78167 (diff)
downloadopen-iov-41f6bf1a07fbf33036d31fe64c98d64cfe621e67.tar.gz
open-iov-41f6bf1a07fbf33036d31fe64c98d64cfe621e67.zip
r576 diag: launch-decision + event-post payload witnesses (gsp_phys_gr_dec_log, gsp_rm_ev_log)
The GR launch-decision dump logs, for the first N draws whose fill saw dropped pages / a partial argument set or whose decision point carries a dstpend/copy-pending verdict: the decision verdicts, the launch's resolved data pages (VA -> guest PA), the live deferred-write records and the pending CE opdef entries - the operand evidence needed to explain a red draw of the readback lottery (the wrong-but-similar page hypothesis). The event-post witness logs every EVENT_POST_EVENT record actually sent with its full payload (hClient/hEvent/notifyIndex/data) and send result, plus a sentinel when post_all_events found valid events but posted none while none were dedup-skipped. This is the evidence needed when a client parks waiting for a completion wake-up that never arrives (the 2nd-client device-state spin): it shows whether the post was generated, for whom, and whether the status-queue write accepted it or dropped it (burst cap / ring full). Both are inert by default (budget 0).
Diffstat (limited to 'wiki/open-iov.org/index.php?title=File:Virgl.png&action=edit.html')
0 files changed, 0 insertions, 0 deletions