diff options
| author | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-27 14:51:47 -0400 |
|---|---|---|
| committer | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-27 14:51:47 -0400 |
| commit | cc47b40c951bbf5c3a9b14e5d07d354cb004d3bd (patch) | |
| tree | feede49ddb1c4933954349b2c63db82ab96877c2 /tools/guest-diag/wall2/wall2_resolver7.py | |
| parent | 182676755e02238f7a767d1249b4878f7cda0d90 (diff) | |
| download | open-iov-cc47b40c951bbf5c3a9b14e5d07d354cb004d3bd.tar.gz open-iov-cc47b40c951bbf5c3a9b14e5d07d354cb004d3bd.zip | |
vgsp: notifier-derived RC-watchdog ring pin (client-init determinism)
The RC-watchdog channel's ring page sits at (notifier_pa page + 0x400) in
every observed boot (r848/r853/r858 data points). The trusted walk resolved
the same ring 14 s late on r858, inside the driver's DMA-test window on the
failing boots, where the ring read zeros/garbage - 'Failed to initialize
DMA' plus guest vmap-lock livelocks followed. Deriving the ring from the
registered notifier PA (guest truth from the channel alloc) removes the
race; the standard entry0+USERD candidate probe still content-gates it.
Diffstat (limited to 'tools/guest-diag/wall2/wall2_resolver7.py')
0 files changed, 0 insertions, 0 deletions