summaryrefslogtreecommitdiffstats
path: root/tools/ghidra/gsp-tu104-570.144/scripts/extract_gsp_version.py
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-11-14 18:16:30 -0500
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-11-14 18:16:30 -0500
commitad1a6bea0c991e429bb2e5b659000ded21cd39f0 (patch)
treeac4aa787e24dc3d9d107748216db61c0cc387393 /tools/ghidra/gsp-tu104-570.144/scripts/extract_gsp_version.py
parentdfc76004dcc680941c8634fce0d7d56d7ae3ad2b (diff)
downloadopen-iov-ad1a6bea0c991e429bb2e5b659000ded21cd39f0.tar.gz
open-iov-ad1a6bea0c991e429bb2e5b659000ded21cd39f0.zip
vgsp: eng43 - keep the MME pack completion record and packed cursor across an owner channel re-register (sema_gl_mme_keep_done_across_recycle, default 0)
c579: the first eng42-module completion (2799/2799) was followed 1.09 s later by the beef owner re-register; the eng40 chan_ctx_reset treated the recycle as a context loss, rewound the pack cursor and wiped pack_done_gen/ch, so every later prelude launch re-emitted (pre_words_out > 0 -> the r1222 clause correctly withheld the release) and MME-PACK-REARM could never fire. The knob keeps pack_done_h/gen/ch and the cursor (pack_off/pack_sa/load accounting) across the re-register so the first prelude launch on the re-incarnated channel is non-emitting and the REARM clause releases the held calls against the engine-resident program. The per-incarnation latch/live/release state is still cleared, and every genuine context wipe (WEDGE-RECOVER/CWD-CLEAR, park recovery, iram-gate failure, non-keep_gen generation rewind, FLR via reload) clears the record on its own path. Default 0 = legacy invalidate (validation pending).
Diffstat (limited to 'tools/ghidra/gsp-tu104-570.144/scripts/extract_gsp_version.py')
0 files changed, 0 insertions, 0 deletions