jan/rrt
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Prioritize peer-site restore caller strip

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 18:47:41 -07:00
commit c28721b5c4
2 changed files with 15 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/rehost-queue.md
View file

@ -72,6 +72,9 @@ Working rule:
selector/fallback bundle before calling `0x00455b70`
- `0x00456072` is a fixed `0x55f2` callback that forwards three local dwords plus unit scalars
into `0x00455b70`
- `0x0045c36e / 0x0045da65 / 0x0045e0fc` are concrete callers of `0x00456100`, repeatedly
allocating `0x23a` rows, forwarding stack-backed buffers, and using the same default scalar
lanes
- `0x00485819` is one typed placed-structure caller of `0x0052edf0` through the generic
three-arg wrapper `0x00530640`
- `0x00490a79` is one chooser-side caller of `0x00455b70`, feeding literal selector
@ -79,7 +82,8 @@ Working rule:
So the next owner question is no longer “what does the acquisition branch do?” or “which post-
load owner replays linked-site refresh?” but “which concrete `0x00455b70` caller family applies
to the live site rows, and which persisted lane becomes the selector bundle that ultimately
seeds `[site+0x04]`?”
seeds `[site+0x04]`?” The current leading restore-family hypothesis is the dense
`0x0045c36e / 0x0045da65 / 0x0045e0fc -> 0x00456100 -> 0x00455b70` strip.
- Make the next static/rehost slice the peer-site rebuild seam above persistence, not another save
scan:
- treat `0x00444690 -> 0x004133b0 -> 0x0040e450 / 0x0040ee10 -> 0x0040edf6 -> 0x00480710` as
@ -90,8 +94,10 @@ Working rule:
- treat `0x00455b70` as the checked-in specialization constructor that maps selector/fallback
bundle lanes into that field owner
- distinguish which `0x00455b70` caller family actually seeds the live site rows before
`0x00420030 / 0x00420280 / 0x0047efe0 / 0x0047fd50` consume the resulting selector, and name
the persisted lane that reaches its selector arg `3`
`0x00420030 / 0x00420280 / 0x0047efe0 / 0x0047fd50` consume the resulting selector, with the
current first target being the dense `0x0045c36e / 0x0045da65 / 0x0045e0fc -> 0x00456100`
family
- name the persisted lane that reaches selector arg `3` inside that wrapper bundle
- Use the higher-layer probes as the standard entry point for the current blocked frontier instead
of generic save scans:
`runtime inspect-periodic-company-service-trace <save.gms>`,