Order placed-structure restore-side stages
This commit is contained in:
parent
8d5fb4f02f
commit
b937ad7e6e
2 changed files with 25 additions and 0 deletions
|
|
@ -210,6 +210,11 @@ Working rule:
|
|||
sweeps live rows through `0x0040ee10`; after that, bring-up proceeds into later route-entry,
|
||||
grid, and tagged refresh owners rather than re-entering the constructor/finalize family
|
||||
`0x004134d0 / 0x0040f6d0 / 0x0040ef10`
|
||||
- the ordinary restore staging order is explicit now too:
|
||||
world bring-up calls the tagged `0x36b1/0x36b2/0x36b3` stream-load owner `0x00413280` at
|
||||
`0x00444467`, refreshes the placed-structure dynamic side buffers through `0x00481210` at
|
||||
`0x004444d8`, and only later enters the queued local-runtime replay owner
|
||||
`0x00444690 -> 0x004133b0 -> 0x0040ee10`
|
||||
- the broader load-side stream owner is separate too:
|
||||
`0x00413280` is the actual tagged `0x36b1/0x36b2/0x36b3` stream-load owner, dispatching
|
||||
per-entry vtable slot `+0x40`; current local recovery still only grounds that seam through the
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue