From 393f1c676d0fc9c7b37ab6a52efe7e2d288d7e90 Mon Sep 17 00:00:00 2001 From: Arthur Hanson Rasmusson Date: Wed, 21 Oct 2026 14:02:15 -0400 Subject: gr: r420b author the guest QMD release on every outcome when release0 is redirected With gsp_phys_rmcall_gr_rel_mod=1 (release0 -> module semaphore, the ordering fix for the engine-release-before-copy-out race) the engine never writes the guest's own QMD release word, so the host must author it on EVERY backend outcome. The hold's success/fail edges do; a launch with no deferred release records (no hold engaged) fell through and its client hung on a word nothing would ever write - the r414 saxpy f0 cur=5 stall. The backend now reports qmd_rel_redirected in the copy result whenever it points release0 at the module semaphore (rel_mod, or no targetable guest release page). svc_fwd_gr_work folds that into the existing gr_rel_unobserved latch, which makes the bounded outcome check author the word on done (success or failure) - the same forward-only write the hold edges perform. rel_mod=0 paths are unchanged (the engine still authors the word and the latch is only set on an unresolved release page). --- tools/cuda-ab/run/transformer | Bin 0 -> 846232 bytes 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100755 tools/cuda-ab/run/transformer (limited to 'tools/cuda-ab/run') diff --git a/tools/cuda-ab/run/transformer b/tools/cuda-ab/run/transformer new file mode 100755 index 0000000..bcde39e Binary files /dev/null and b/tools/cuda-ab/run/transformer differ -- cgit v1.2.3