diff options
| author | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-20 20:04:02 -0400 |
|---|---|---|
| committer | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-20 20:04:02 -0400 |
| commit | 03275eae56dc37e2b6bb4d50052648256af80f60 (patch) | |
| tree | 3535239b388b808c1b8ebdced2e28b4705785c9b /wiki/System-Overview.md | |
| parent | db0c982b954e4782dff4d22d1673f04edac54770 (diff) | |
| download | open-iov-03275eae56dc37e2b6bb4d50052648256af80f60.tar.gz open-iov-03275eae56dc37e2b6bb4d50052648256af80f60.zip | |
sema: r384b narrow the fill pin-demand hold to SYS (guest RAM) resolutions + FILL-EXEC witness
- The r384 boot held a large fill whose walk resolution was VID (the
emulated vidmem shadow) - the hold was pointless overhead there and
the re-decode re-resolves (the resolver is non-deterministic), so the
hold now applies only when the fill would land in guest RAM (SYS
aperture), the class that zeroed the guest's page-table pages. Shadow
resolutions stay immediate.
- FILL-EXEC witness (bounded 64/boot): va, pa, aperture, provenance and
pattern of every >= 4 KiB virtual fill execution - the decisive line
for the boot-corruption forensics; the large zero fills were invisible
until now.
Diffstat (limited to 'wiki/System-Overview.md')
0 files changed, 0 insertions, 0 deletions
