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

Prioritize save-backed peer-site selector strip

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-18 18:51:03 -07:00
commit 8812b2f6a1
2 changed files with 16 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/rehost-queue.md
View file

@ -78,6 +78,10 @@ Working rule:
- the `0x00456100 -> 0x00455b70` wrapper mapping is now grounded far enough to say the sampled
selector-source lanes are `[owner+0x23e]` at `0x0045c36e`, literal zero at `0x0045da65`, and
`[ebp+0x08]` at `0x0045e0fc`
- direct disassembly now shows `0x0045c150` as a save-backed loader for `[owner+0x23e/+0x242]`:
it zeroes those fields, runs the shared tagged loader `0x00455fc0`, reads tagged payload
`0x5dc1`, and copies the two recovered lanes into `[owner+0x23e/+0x242]` before
`0x0045c310 -> 0x0045c36e` later feeds `[owner+0x23e]` into `0x00456100`
- `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
@ -85,8 +89,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]`?” The current leading restore-family hypothesis is the dense
`0x0045c36e / 0x0045da65 / 0x0045e0fc -> 0x00456100 -> 0x00455b70` strip.
seeds `[site+0x04]`?” The current strongest restore-family hypothesis is now the save-backed
`0x0045c150 -> 0x0045c310 -> 0x0045c36e -> 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
@ -98,10 +102,10 @@ Working rule:
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, with the
current first target being the dense `0x0045c36e / 0x0045da65 / 0x0045e0fc -> 0x00456100`
family
- name which of the currently sampled selector-source lanes (`[owner+0x23e]`, literal zero, or
`[ebp+0x08]`) reaches selector arg `3` for the live site rows
current first target being the save-backed
`0x0045c150 -> 0x0045c310 -> 0x0045c36e -> 0x00456100` family
- confirm that this save-backed owner family is the same class-0 site family consumed by
`0x00420030 / 0x00420280 / 0x0047efe0 / 0x0047fd50`
- 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>`,