summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAge
* vgsp: eng89d - admit the draw on a bind from another channelArthur Hanson Rasmusson7 hours
| | | | | | | | | c910 proved the persisted bind arrives on the X/2D channel (RT-PERSIST h=0x1000013 B=0x20400000 W=0x780 H=0x438) while the beef draw window is on 0xbeef0100, so the eng89c channel equality refused the exact window it was meant to admit. The stored channel is now diagnostic only; the draw-marker guard, the surface-class validity and the per-session clear remain.
* vgsp: eng89c - fix the live GS map, draw anchor, prelude budget, RT persistenceArthur Hanson Rasmusson7 hours
| | | | | | | | | | | | | | | | | | | | | | | | | Four fixes from a code audit of eng89/eng89b, each of which could have made the maps=6 experiment unobservable or harmful: - Draw-move anchor: use the FIRST 0x3810 run only. The 247-word window also carries its own 0x3810 later; the old code moved the draw to the last one, i.e. behind the setup calls it must precede. Removed the post-scan promotion. - Prelude/stage budget: the raster-enable words (8) pushed the prelude toward the 96-word cap and could skip the whole stage-bind block (SPH-BIND-STAGE-SKIP reason=budget), hiding the GS bind. Array and gates grown to 128. - RT persistence: require B/W/H only (A optional, matching the existing first-valid check), store the channel and require it for admission, require a real draw marker (0x1618/0xd78/0x3910) in the window, and clear the state in svc_session_flush so a recycled channel cannot inherit a dead session's target. - GS live map: moved out of the SPH-AUTHOR copy branch and derived from the family page's actual VTG image at +0x900 (not the source record), so an overlap skip no longer makes maps=6 inert. New gs_addr=0 parameter set (GS at 0x780) keeps the GS header clear of the VTG copy. Test matrix: params-r1624-maps6-780.txt (maps=6, gs_addr=0).
* sdl_cap: capture-mode and file-ownership fixes for the GZDoom video runArthur Hanson Rasmusson7 hours
| | | | | | | | | | | | | | | | | | - GZCAP_SYNC=1: synchronous readback path for software GL (the async PBO+fence path never signals under Mesa llvmpipe, so 0 frames were recorded; the GPU path keeps the async path). - GZCAP_READBUF=back: read GL_BACK on a double-buffered X11 window (Xvfb); the default GL_FRONT is correct only for the single-buffered GPU pbuffer. Without it every Xvfb frame was black. - File gate: only an SDL renderer process opens the capture, and an existing non-empty capture is appended, never truncated. The old 'wb' open in every LD_PRELOAD child turned a 288-frame capture into a 4108-byte file; a helper without SDL also opened it via the glReadPixels fallback. - Log the read buffer in the async arm line. Validated by the 2026-11-16 GZDoom video runs: 2200-frame captures, clean_end=1, corrupt=0, 30 fps encodes, delivered via files.vgpu.io.
* vgsp: eng89b - persist the colour-target bind across pushesArthur Hanson Rasmusson9 hours
| | | | | | | | | | | | Most beef draw pushes carry no colour-target bind of their own (the client binds the target once per context/target switch in an earlier state push), so the per-window admission refused the real frame pushes on most boots ('beef draw-synth: no valid last colour-target bind', the shallow-boot lottery). Track the last complete, plausible bind seen on a trusted push (same surface-class validity as the first-bind check; an invalid later write never overwrites a valid state) and admit a beef draw window on it: RT-PERSIST + '3D mark admitted (persisted colour-target bind)' receipts. Knob sema_gl_win_rt_persist, default 1.
* vgsp: eng89 - live-derived GS map, draw-move anchor, raster enables, async ↵Arthur Hanson Rasmusson9 hours
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | capture Kernel (deterministic fixes, each with an A/B knob): - sema_gl_sph_gs_maps=6: derive the whole 216-bit GS IMAP/OMAP blocks from the bound VTG image's OMAP and the PS image's IMAP at authoring time (SPH-GS-MAP receipt; SPH-GS-SKIP names ps-invalid/gs-invalid/ vtg-overlap/vtg-short). maps=4 stays as the fallback. - DS-MAP census line: dump stage-4/5 w5/w10/w13/w17 next to DS-IMAGE so the fetched maps are visible without a new probe. - MME pack carrier: reject maxa > 4096 (the IR pack array) instead of 64K, with MME-PACK-REJECT reason=bound. - MME-DRAW-MOVE: anchor the slot-34 move after a 0x3810 VERTEX_STREAM run. c848 moved CALL(34) to 0x204, ahead of the prepended stream bind, so the 8x3 fetch used stale stream state. - sema_gl_raster_enable=1: emit SET_RASTER_ENABLE=1 and SET_GLOBAL_RENDER_ENABLE MODE_TRUE in the raster prelude (fresh replay contexts may carry 0 for both, discarding every fragment). Guest tooling (unblocks the render loop and capture): - sdl_cap.c: asynchronous PBO+fence capture with a 5 s abandonment bound; no glFinish/blocking readback (c899 wedged gzdoom in an uninterruptible nv ioctl); clean sentinel from a destructor. - gz_pbuf.c: request depth 24/stencil 8, log GL_DEPTH_BITS, and swap with glFlush only. - mission-gz.sh: gl_frames probe off by default; GZDoom launched detached with a bounded wait, per-attempt X restart and retry; capture in /dev/shm with GZCAP_MAXF. - gzdoom_pbuf_run.sh: gl_pipeline_depth=2, gl_finishbeforeswap=0, GZCAP_MAXF default, rc-file support for the detached run. - run_cycles_long.sh: durable multi-cycle runner (the previous one lived in /tmp and was lost on reboot); pushes tools, runs the mission, grabs dmesg + guest logs + capture per cycle, stops on pixels. Test matrix: params-r1624-maps{4,6}.txt.
* vgsp: eng88 - reject absurd pack totals before arming the carrierArthur Hanson Rasmusson13 hours
| | | | | | | | CONT.549/c890: MME-PRELUDE pack-part decoded the packed program's length word to 0x3D2F5F73-like garbage (1602/1026586419, expected /2799) and the carrier armed a continuation on it. gsp_phys_gr_mme_ carry_arm() now refuses maxa==0 or maxa>64K, so a corrupt length can never arm a bogus pack continuation.
* vgsp: eng87 - do not consume the carrier when the forward slot is busyArthur Hanson Rasmusson13 hours
| | | | | | | | | CONT.548/c886: a clean 247 window (VS-BIND base=0x450c1f4) reached MME-CARRY-FIRE gen=4 and was immediately cancelled with reason= request-busy: svc_gr_carrier_request() claimed the armed carrier (the take clears the arm) before taking the forwarding slot, so the lost slot lock left the pack uncompleted. Probe SVC_FWD_INFLIGHT before the take so the retryable busy case returns without consuming the arm.
* vgsp: eng86 - pack carrier self-candidate (fire without a client launch)Arthur Hanson Rasmusson13 hours
| | | | | | | | | | | | | | CONT.545/c880: the armed pack carrier (MME-CARRY-ARM gen=3 off=1506/2799) never fired because the pump needs a matching CLIENT beef candidate and the 2-frame mission ended before one re-appeared; it expired with no FIRE/CANCEL/WAIT receipt. The pump's carry block now, when there is no candidate but the channel's golden pack is still contiguously loaded (gsp_phys_gr_mme_carry_ctx_alive: pack_load_h==carry_h && golden ready), submits svc_gr_carrier_request() as its own synthetic candidate (MME-CARRY-FIRE reason=self-candidate). A truly gone context is reported MME-CARRY-CANCEL reason=ctx-gone, never silent. Release stays beef-only; the eng68 chain still runs after the carrier fire (pack complete -> release replay -> mac=0x22).
* tools: GS-map A/B - per-boot maps=0 (short 2-frame draw-carrying cycles)Arthur Hanson Rasmusson13 hours
|
* vgsp: eng85 - owner-channel MME pack continuation ↵Arthur Hanson Rasmusson14 hours
| | | | | | | | | | | | | | | | | | (sema_gl_mme_pack_carry_client) CONT.539: c858's split pack landed on the client channel h=0x1000013 and the continuation never armed because gsp_phys_gr_mme_carry_arm() required (h & 0xfffff000)==0xbeef0000. c848 only worked because the same bytes landed on h=0xbeef0100. New knob sema_gl_mme_pack_carry_client (default 0) relaxes the arm and take gates to the split's own owner channel; the synthetic windowless LOAD-ONLY launch still goes through that owner's forwarding candidate (the pump locates it by h_object), and the builder reads the global pack cursor so the continuation bytes are identical. The saved-window release carrier stays beef-only; its MME-CARRY-ARM mode=release fires once the pack becomes resident (the owner completion clears the pack-not-resident gate on the next pass). Params-r1624 enables it.
* tools: dedupe the raster-prelude param (it was already inline =1)Arthur Hanson Rasmusson14 hours
| | | | | | | The previous commit appended a duplicate; the inline line-1 params already carried sema_gl_raster_prelude=1, so c848 ran WITH the raster prelude and still saw the SPH18 DS with no stores - the scissor/depth is not the remaining gate; the GS SPH18 is.
* tools: enable the raster prelude (CT_WRITE + depth/stencil/scissor disables)Arthur Hanson Rasmusson14 hours
| | | | | | | | | | | Plan B from CONT.538: the 247 window carries 0x12cc/0x12e8/0x1380=0 (SET_DEPTH_TEST / SET_DEPTH_WRITE / SET_STENCIL_TEST, per the code comment at the knob) and no SET_CT_WRITE / SET_SCISSOR_ENABLE - those are client channel state. On a replayed 3D DRAW_IAB the replay channel keeps hardware defaults, so every fragment can be discarded (CT_WRITE=0). Enable the existing sema_gl_raster_prelude remedy (CT_WRITE(0..7)=0x1111, depth/stencil disable, SCISSOR_ENABLE(0)) alongside gs_img=1/maps=2/TCS-off.
* tools: GS-map A/B step 2 - sema_gl_sph_gs_maps=2 (PS-exact IMAP)Arthur Hanson Rasmusson14 hours
| | | | | | | | c850-c853 (maps=0, pass-through): the 247-window-class boot did not reproduce in these cycles (c850 no release, c851 poison 0xbadf1201, c852 a 730-page upload burst with no DRAW_IAB release lines), so the SPH18 read needs a maps=0 247 boot that did not occur. Step 2 of the A/B per the plan: maps=2 (IMAP PS-exact) with gs_img=1 and TCS off.
* tools: GS-map A/B step 1 - sema_gl_sph_gs_maps=0 (pass-through)Arthur Hanson Rasmusson14 hours
| | | | | | | | c848: with the correct VTG VB base the DRAW_IAB runs and the hardware DS now flags SPH18 (GS check2): DS-FAST ds 80000000->81040000. The header-only GS SPH (gs_img=1, family+0xe80) with maps=4 (the r1569 variant) still fails the GS attribute-map check. Step 1 of the A/B: maps=0 (pass-through IMAP/OMAP). Keep TCS off (stage_disable=0x04).
* vgsp: eng84 - prepend the VTG stream state at release fire timeArthur Hanson Rasmusson14 hours
| | | | | | | | | | | | | c846: the 150-window release fired with VS0=0 because the held window was saved before the client's VERTEX_STREAM CALL(2) was captured (0x3810 lives in a later push); the dispatch-time sticky payload (end=0x450d100 base=0x450b5dc) arrived after the save. The release fire happens seconds later, so build the state in gsp_phys_gr_mme_release_fill: with the current 5-word payload, prepend [0x1c00 fmt=0x1014, base] + [0x600 size=end-base] + [0x3810 the full 5-word call] to the saved window, skipping anything it already carries. MME-VS-FILL receipt; the normal patch relocates the pair and the 0x3810 range.
* vgsp: eng83 - decode the 0x3810 payload shape: base is d[4], end is d[2]Arthur Hanson Rasmusson14 hours
| | | | | | | | | | | | | | | | | | | | | c836 proved the client's VERTEX_STREAM CALL(2) payload is [stream, end_hi, end_lo, base_hi, base_lo] (MME-VSTREAM: end=0x1e02100 base=0x1e001f4, MME-VSTREAM-LINE base=0x450c1f4 end=0x450e100 pages=3 first8=...3f800000 3e4ccccd...). eng79 wrongly took d[2] (the END 0x450e100, a zero page) as the stream base; the base d[4]=0x450c1f4 carries the float2 vertices. The Doris slot-2 sim with the full 5-word payload emits LOCATION 0x1c08<-base and SIZE 0x604<-end-base. - service: svc_gl_vs_call[5] (getter out[5]) - capture v0..v4, log 5 words; eng82 page-set collection adds the end (v2) and base (v4). - booter eng79: slot-2 base = vcall[4] (require vcall[1]==0, vcall[3]==0, aligned), end = vcall[2]; size pair = end-base; receipt base=.. end=..; VS-BLOB2 dumps at the base. - booter eng77: emit the FULL 5-word 0x3810 call (op=5 cnt=5) even when the window carries its own call (the slot-34 reorder moves the draw ahead of it); the 0x3810 MME-VSTREAM patch maps [base,end] into one contiguous shadow line.
* vgsp: eng82 - collect the CALL(2) VERTEX_STREAM VB VA into the GL page setArthur Hanson Rasmusson16 hours
| | | | | | | | | | | | | c840: VS-BLOB2 va=0x450e100 unresolved - the slot-2 VERTEX_STREAM payload's VB page (0x450e000) was never part of the forwarded launch's page set, so the sema resolver cannot map it and the synthesized stream-location pair cannot be relocated (the engine would fetch an unmapped guest VA). svc_gl_field now handles 0x3810: every plausible address word (>=0x100000, <2^40, 4-byte aligned) in the CALL(2) payload is added via svc_gl_add_ptr, so the candidate/forward page set includes the VB page and the release's pair relocation can resolve it.
* vgsp: eng81 - dump the 480 B VB block at the bound CALL(2) VAArthur Hanson Rasmusson16 hours
| | | | | | | | The slot-2 VERTEX_STREAM VA (0x450e100) is now bound as the stream location; the release still stores nothing. Dump the first 64 B of the client VB (resolved HPA) at save time (VS-BLOB2) so the 24x20 B float2 vertex payload is verifiable/rejectable, and compare the relocated shadow (VS0) against pagebase+client_offset (the suspected 0xf4 skew).
* vgsp: eng80 - prefer the window carrying the VERTEX_STREAM CALL(2)Arthur Hanson Rasmusson17 hours
| | | | | | | | | | | | | c835: the 151-word DRAW window (slot 34, no 0x3810 call) was saved and released; the client's VERTEX_STREAM_TURING CALL(2) was captured 11 s later from the 247-word state push, too late for that save. The 247-word window carries BOTH slot 34 and the 0x3810 call (relocated d2=0x1e22100). release_save now supersedes a saved record without a 0x3810 run when the new window carries one, so the release uses the window that has the VTG stream state (and eng79's slot-2 VA synth pair can bind the real VB base).
* vgsp: eng79 - bind the stream location to the CALL(2) VERTEX_STREAM VAArthur Hanson Rasmusson17 hours
| | | | | | | | | | | | The client's VERTEX_STREAM_TURING CALL(2) payload [0,0,0x0450e100] carries the real VTG vertex buffer VA; the slot-2 macro itself emits location=0 / size=<VA> (Mesa slot-2 sim), i.e. the base is never written to 0x1c04/0x1c08. Synthesize the stream-location pair with the CALL(2) VA as the base instead: release_save takes gsp_sema_gl_vs_call() and, for stream 0, prefers payload[2] (masked) over the scanned CB candidate, emitting the usual [fmt=0x1014, upper, lower] pair + the size pair. The patch relocates the VA like any 0x1c00 pair. MME-VS-BIND receipt gains src=slot2|scan|sticky.
* vgsp: eng78 - raise the census hit/line budget (0x3808 staging-buffer call)Arthur Hanson Rasmusson17 hours
| | | | | | | The 16-hit cap hid later CALL slots (the VARRAY_STAGING_BUF_TURING slot 1 / 0x3808 base binder) in the 728-byte beef push. 32 hits and a 1600-byte line keep the whole 0x100..0x1ff + 0x3800..0x39fc set in one receipt.
* vgsp: eng77 - capture and replay the client's VERTEX_STREAM_TURING CALL(2)Arthur Hanson Rasmusson17 hours
| | | | | | | | | | | | | | | | | | The beef 728-byte push carries CALL_MME_MACRO(2) (method 0x3810, golden slot 2 = VERTEX_STREAM_TURING) with payload [0,0,0x0450e100]: the Mesa mme_tu104_sim of golden slot 2 with those args emits SET_VERTEX_STREAM_A_LOCATION 0x1c04<-0, 0x1c08<-0, and the Turing size pair 0x600<-0, 0x604<-<the VA> - the VTG stream state the per-frame DRAW window slices omit. The census (eng76, 0x100..0x1ff) finds it at 0x148 of the 728 push; the 247-word window carries the relocated call at 0x2e0 (d2=0x1e22100), the 151-word DRAW window does not. - service: sticky svc_gl_vs_call[3] from every 0x3810 run (VS-CALL receipt), getter gsp_sema_gl_vs_call(). - booter release_save: when the window has no 0x3810 run, prepend the captured ONE_INCR run (0x3810<-payload) ahead of the DRAW window; the normal patch relocates the VA payload (sema_gl_mme_reloc). - vs_pre buffer 12->24 words. Census range stays 0x100..0x1ff (eng76).
* vgsp: eng76 - census the full 0x100..0x1ff method familyArthur Hanson Rasmusson17 hours
| | | | | | | | The beef pushes carry 0x114/0x11c/0x124 runs; extend sema_mme_census from 0x114..0x124 to the whole 0x100..0x1ff page so every setup method in that family (3 data words/hit) is visible in the beef windows (128/151/247/324/491 words) and the X 221-word window. The existing 0x1c00..0x1cf8/0x600..0x61c ranges stay in the same line.
* vgsp: eng75 - A/B: point the SURF prelude/RT0 at the big-surface aliasArthur Hanson Rasmusson18 hours
| | | | | | | | | | | | | | c824/c825: the release RT0/RT1 target is 0xa000000 (the data-rec bounce base from gsp_phys_gr_surf_launch_target's rec-over-alias preference) while the aliased 1920x1080 X-screen surface is 0x15d0000 (2025 pages). The changed pages (0x120700000/0x120704000/0x120705000) are inside the screen range but the draw's RT offsets are computed against the bounce base. sema_gl_surf_alias_pref (default 0; params=1): after the SURF prelude patch, rewrite its target words to gsp_phys_gr_surf[].alias so the prelude and the RT0 copy (r1483) both name the contiguous surface alias. SURF-ALIAS-PREF receipt.
* tools: revert sema_gl_raster_extra (poisoned before the release in c794/c829)Arthur Hanson Rasmusson18 hours
| | | | | | | The raster-kill A/B never reached a release: c794 and c829 both hit the badf1201 held-window poison before the release. Revert the param to the known-good TCS-off + vs_autobind configuration; the raster_extra hypothesis stays open for a clean-boot A/B.
* tools: enable sema_gl_raster_extra for the raster-kill A/B (eng74 build)Arthur Hanson Rasmusson18 hours
| | | | | | | | The release now binds VS0/SZ0 (scanned float2 vertex data), viewport and RT, runs the DRAW_IAB, but no surface page changes. The neutral blend/alpha/cull/point/ZCULL state is the untested fragment-kill lever (c794 poisoned before the release); re-enable it in params for the c828+ A/B.
* docs(wiki): 2026-11-16 status refresh - DRAW_IAB mac=0x22 executes end to ↵Arthur Hanson Rasmusson18 hours
| | | | end (c788); TCS-off DS clean; remaining blockers are the vertex buffer (eng74 VS-BLOB) and render-target store/alias visibility (eng74 alias WIT); stores still 0
* vgsp: eng74 - dump the scanned VS candidate and witness the surface alias pagesArthur Hanson Rasmusson18 hours
| | | | | | | | | | | | | | 1. VS-BLOB: on a VS-SCAN candidate, print the 16 words at the winning block and the DRAW range (starts 0,3,..,21 * stride 20 + 8), so the CB-page heuristic candidate can be validated/rejected against the Mesa DRAW_IAB shape. 2. Surface alias WIT: gsp_phys_gr_surface_alias_locked records every RT guest page (VA+HPA) it maps in a persistent table; the launch WIT capture notes them, so a render-target store through the 0xa/0xc alias becomes a GUEST-WIT changed line. This fixes the eng73 gap (the surface alias does not use the pair alias cache). params: sema_gl_wit_shown=40 so the RT page is not hidden by the 4-line budget.
* vgsp: eng73 - witness the big-surface alias pages in GUEST-WITArthur Hanson Rasmusson23 hours
| | | | | | | | | | | c819: VS0=0x1e101f4 and SZ0=0x1f0c are bound on the release and the DRAW_IAB runs, but the GUEST-WIT changes are the release/report pages (0x4238000, 0x41a1000) and the 2 operand pages - the render target is written through the big-surface ALIAS (RT0 target 0xa000000/0xc000000), whose HPAs are the client's surface pages, not any tracked data record or req->pages entry. Add every mapped surface alias page (alias VA 0xa000000..0xdffffff) to the witness set; an RT store then appears as GUEST-WIT changed on an alias VA.
* vgsp: eng72 - witness the launch operand pages in GUEST-WIT (RT store ↵Arthur Hanson Rasmusson23 hours
| | | | | | | | | | | | visibility) The c817 release now binds VS0 (relocated shadow 0x1e107d0) and SIZE (0x1930) and runs the DRAW_IAB, but the no-writes tracker still reads 0/1025: the RT0 alias page (target 0xc000000 in c817) is one of the launch's req->pages operands, not one of the 1025 tracked data records, so an RT store is invisible to both the bounce scan and GUEST-WIT. Add the req->pages guest VAs/HPAs to the WIT set; a change on the RT page becomes the direct store witness.
* vgsp: eng71c - bind the scanned vertex page by guest VA so the patch ↵Arthur Hanson Rasmusson24 hours
| | | | | | | | | | | | | | relocates it c816: the VS-SCAN candidate bound by the data page's server-managed reloc_va (0xa300310); the window patch's pair resolver did not know that VA, the launch hit MISS-ABORT and the release aborted (MME-CARRY-ABORT mode=release reason=hw-error rc=-42). Use the tracked data page's GUEST VA + offset (0x1204xxxxx+off) instead: gsp_phys_rmcall_gr_3d_reloc checks req->data/req->pages and rewrites the pair to an engine-visible shadow (same HPA), so the bound range is fetchable and the MISS-ABORT is avoided.
* vgsp: eng71b - also emit the Turing stream size when the window carries VSArthur Hanson Rasmusson24 hours
| | | | | | | | | | | | | c814 (eng70): a 491-word release window has VS0=0x1020/0/01e90000 and VS1=0x1020/0/01e9000c (real stream binds) and VA=0xd74=0x08, but SZ0=0 and wrote=0. The Turing stream SIZE pair (0x600/0x604) is client channel state the replay never receives; a zero size can clamp the fetch to zero vertices. Always prepend the size pair (0x600<-0, 0x604<-0x100000) on release saves with sema_gl_vs_autobind>=2 when the window has no 0x600 run, even when its own VS location is present (MME-VS-SIZE ... (window has VS) receipt).
* vgsp: eng71 - scan the tracked data pages for the vertex payload and bind VS0Arthur Hanson Rasmusson24 hours
| | | | | | | | | | | | | | | | c812/c813: the 151-word DRAW-window release has VS0=VS1=VS3=0 and SZ0=SZ1=SZ3=0; the DRAW_IAB emits its 8x3-vertex draws (VA=0xd74=0x15) against no vertex stream, so nothing rasterizes. The client's vertex payload is a 24-vertex, 20-byte-stride float2 buffer (FORMAT 0x1014, ATTR(0) float2 offset 0) written into the launch's tracked data pages. sema_gl_vs_autobind (0=off, 1=scan+log, 2=bind; params=2): scan the 0x120400000..0x120800000 data pages for a 512-byte block of 24 plausible float2 vertices (score>=8 nice values), then prepend to the saved release window: VS0 location [fmt=0x1014, upper, lower=reloc_va +off], and the Turing stream SIZE pair (0x600<-0, 0x604<-0x100000). VS-SCAN/MME-VS-BIND/MME-VS-SIZE receipts; the starts 0..21 x stride 20 resolve inside the 1 MB bound.
* vgsp: eng70 - census the vertex-stream family and dump VS size/attribute stateArthur Hanson Rasmusson24 hours
| | | | | | | | | | The per-draw VB bind is still located: extend sema_mme_census to 0x1c00..0x1cf8 (vertex stream FORMAT/LOCATION/SIZE) and 0x600..0x61c (stream sizes), print up to 3 data words per hit (the location pairs need UPPER,LOWER), and add a second DRAW-STATE line with the stream sizes (SZ0/SZ1/SZ3) and the first SET_VERTEX_ATTRIBUTE_A(0..2) words (ATTR0), so a zero-size stream or a mismatched attribute format is visible next to VS0 and the viewport.
* vgsp: eng69b - also capture the split SET_VERTEX_STREAM_A_LOCATION_A/B shapeArthur Hanson Rasmusson24 hours
| | | | | | | | The driver may bind the vertex stream as LOCATION_A(j) (0x1c04+j*0x10, [UPPER, LOWER]) plus LOCATION_B(j) (0x1c08+j*0x10, [LOWER]) instead of the combined [FORMAT, UPPER, LOWER] run at 0x1c00. Track the A upper byte per stream and publish the same sticky base for either shape, so eng69's release-window prepend works for both client encodings.
* vgsp: eng69 - persist and replay the client's vertex-stream location pairsArthur Hanson Rasmusson24 hours
| | | | | | | | | | | | | | | | | | c807: the release DRAW window carries only SET_VERTEX_STREAM_A_FORMAT (0x1c00 <- 0x1014); its [fmt, UPPER, LOWER] location pair lives in the client's setup push, so the replay context's stream address is unbound (DRAW-STATE VS0=0) and the 8x3-vertex DRAW_IAB fetches nothing (wrote=0). - service: sticky svc_gl_vs_base[8] from every decoded 0x1c00..0x1cf0 count>=3 pair (VS-BIND receipt); re-add those pages to every GL draw section's candidate page set so the launch can map them; getter gsp_sema_gl_vs_base(). - booter release_save: when the held window carries the FORMAT but no count>=3 location pair, prepend a normal INC run [fmt, UPPER, LOWER] for streams 0 and 3 to the saved window (MME-VS-BIND synth receipt, MME-CARRY-SAVE vs_pre=N). The normal window patch relocates the pair to a shadow VA using the saved page set, so the release draw can fetch its vertices.
* vgsp: eng68 - chain the release after any GR launch that leaves it owedArthur Hanson Rasmusson25 hours
| | | | | | | | | | | | | | | c796: the release armed (MME-CARRY-ARM mode=release, held=68) when the client's own launch completed the pack, but that launch's poll owned the forwarding slot; the beef channel unregistered 0.99 s later (+0.1 s ARM) and the release only saw request-inflight/no-channel. The client's pack-completing launch is often its last push. Generalize eng64's chain: after ANY successful GR launch of the release's own beef handle, if the release is still owed (gsp_phys_gr_mme_release_owed_for), wait the settle grace in the same slot, claim and run the release work directly. The synthetic pack carrier path is unchanged; the release work still owns the outcome publish and INFLIGHT clear.
* vgsp: eng67 - synthesize a full-RT viewport for replayed beef 3D windowsArthur Hanson Rasmusson25 hours
| | | | | | | | | | | | | | | | | c797 (engine ef2e68b9) DRAW-STATE on the release launch: RT0/RT1 = alias 0xa000000, 1920x1080, fmt 0xe6; VS0 address 0x1e305dc bound; DRAW_IAB emitted its last vertex-array start (0xd74=0x15); but the viewport SCALE/OFFSET methods 0xa00..0xa14 read 0 on the replay context (they are client channel state the per-frame window never carries). Every vertex maps to (0,0), so the 8x3-vertex draws rasterize nothing and the 1025 tracked RT pages stay 0. sema_gl_viewport (default 0; params=1) emits a full-color-target viewport before beef 3D windows: SCALE_X=+W/2, SCALE_Y=-H/2, SCALE_Z=0.5, OFFSET_X=W/2, OFFSET_Y=H/2, OFFSET_Z=0.5 (IEEE bits computed without FP; W/H from the RT0 method shadow, fallback 1920x1080). VIEWPORT receipt carries the emitted bit patterns.
* vgsp: eng66 - DRAW_IAB raster-state census and CALL(34) arg dumpArthur Hanson Rasmusson25 hours
| | | | | | | | | | | | | | | | | | | Mesa mme_tu104_sim replay of the golden slot-34 body with the c788 CALL args [4,8,3,6,9,12,15,18,21,24] emits 8 draw sequences: BEGIN(0x1618)<-4, SET_VERTEX_ARRAY_START(0xd74)<-{0,3,...,21}, DRAW_VERTEX_ARRAY(0xd78)<-3, END(0x1614)<-0. The draw is issued; the stores stay 0, so the next question is the raster state the emitted draw consumes. - MME-CALL-ARGS: dump the slot-34 CALL payload at the held-window census (Mesa sim input, replayable offline). - DRAW-STATE (one-shot per release launch, after GUEST GR LAUNCH OK): color target 0/1 (0x800..0x810/0x840..0x850), vertex streams (0x1c00/0x1c04/0x1c08/0x1c0c, 0x1c10/.., 0x1c30/..), viewport (0xa00..), the BEGIN/END draw pair (0x270/0x274) and the emitted 0xd74/0xd78 through the C597 method shadow. Diagnostic only; no emission change.
* vgsp: eng65 - allow per-stage SPH disable on the all-slots bind boot ↵Arthur Hanson Rasmusson26 hours
| | | | | | | | | | | | | | | | | (TCS-off DS A/B) c788 achieved DRAW_IAB (MME-FAST macro-status=00122266 mpc=614 mac=0x22 run=1 via MME-DRAW-MOVE) but the draw latched DS 0x84000420 (SPH5 VSB c1, SPH10 TCS c2, M_PIPE_STAGE TI) and stores stayed 0 (NOWRITE-CONFIRMED wrote=0). The DS-ESR post-clear=84000420 then the retire reads ds=80000000, so the pending validation error is the draw's. The per-stage disable mask was only honoured with sema_gl_sph_bind=0, so the all-slots boot could not disable TCS while keeping the window's own VSB bind and the other synth slots. Read the mask unconditionally; default 0 keeps the emitted bytes identical. params-r1624 sets sema_gl_sph_stage_disable=0x04 (TCS disable record 0x2080<-0x20, synth j2 bind skipped) for the next A/B.
* docs(wiki): 2026-11-15 evening status refresh - held-window release carrier ↵Arthur Hanson Rasmusson26 hours
| | | | deterministic (c772), slot-34/SA[34] settled (0x265), call order is the blocker; eng64 chains the release behind the pack carrier; STATE-CURRENT snapshot
* vgsp: eng64 - chain the release behind the pack carrier and name a stalled ↵Arthur Hanson Rasmusson26 hours
| | | | | | | | | | | | | | | | | | | | | | carrier's gate c779: the pack-continuation carrier completed the pack (MME-CARRY-COMPLETE gen=4 off=2799/2799) and armed the release (MME-CARRY-ARM mode=release), but its launch poll held the single forwarding slot for 2801 ms; the armed release then deferred request-inflight until the beef channel unregistered at +2.2 s, so the release ended in MME-CARRY-HOLD reason=no-channel. - svc_fwd_gr_work: after a successful synthetic pack carrier, wait out the release grace in the same slot, claim it and run the release work directly (chained MME-CARRY-FIRE mode=release ... receipt). Gate: sema_gl_mme_release_chain (default 1; release carrier still default 0). - pump pack-carry block: an armed due carrier that cannot go out now names its blocker (MME-CARRY-WAIT reason=no-channel/client-candidate/ request-inflight/fe-defer), so the c781-class silent stall is visible. - booter: gsp_phys_gr_mme_release_waiting()/chain_enabled() helpers. c783-c785 (a03a68ea build) were all shallow (author=0, no MME window).
* vgsp: eng63b - reorder the release window's slot-34 DRAW_IAB call ahead of ↵Arthur Hanson Rasmusson26 hours
| | | | | | | | | | | | | | | | | the setup calls c780 (9a087063): the release launch ran and MME-SA-REARM re-pointed 7 slots (slot 34 client=0x265 golden=0x265), but the replay executed mac=0x33/0x0/0x39 only. The 728 B state window carries the slot-34 CALL at off=0x340 AFTER its 0x33/0x39 setup calls; the earlier 0x39 macro latches DS 0x84000420 and the MFE never reaches CALL(34) (mme mac stays 0x39, then idle). c716's 324 B DRAW window puts CALL(34) first and ran mac=0x22. Release launches only (release_sa_arm): locate the window's first CALL run and the slot-34 run (+ its immediately preceding 0x1644 pair), and emit the window with that run moved ahead of the first CALL run. MME-DRAW-PLAN/MOVE receipts; default off path unchanged.
* vgsp: eng63 - held-CALL target census, DRAW-window preference, and ↵Arthur Hanson Rasmusson27 hours
| | | | | | | | | | | | | | | | | | | | | | | | release-launch SA re-arm c776 proved the saved-window release replay carries the slot-34 CALL_MME_MACRO run (MME-WINRUN off=340 op=5 cnt=10 mthd=3910) but the macros ran 0x33/0x0/0x39: the release launch sets emit_prelude=0, and the client capture had no slot 34 (c774 fill published golden entry 0x265 host-side only), so the stale engine SA[34] resolved the call to IR 0 (mac=0x0). - MME-CALL-CENSUS/MME-CALL-TARGET: decode the held window's CALL runs with the hold/drop run grammar (op 1/3 walk method+4k, op 5 only the header method, op 4 one method) and print targets + slot34 with the client/golden/used entry. - release_save: among DRAW_IAB-bearing windows prefer the smaller raw DRAW stream (324 B/81 words, the c716 mac=0x22 shape) over the 728 B state window; keep=draw-win receipt. - sema_gl_mme_release_sa_arm (default 0; params-r1624 enables it): run the SA re-arm + golden fill on the release launch so CALL_MME_MACRO(34) points at the golden DRAW_IAB body (IR 0x265). Pack-carry/release receipts unchanged; release carrier still default 0.
* tools/guest-diag: tag BGRA capture records as GZF2 fmt 33Arthur Hanson Rasmusson27 hours
| | | | | | | | | | | | | | | sdl_cap.c wrote the same 32 in the GZF2 record format field for every capture path, so gzf2_video.py's auto mode decoded ARGB8888/X-surface frames (BGRA byte order on little-endian) as RGBA and swapped red and blue. Make the field the documented pixel-order tag: 32 = RGBA8 from the GL swap path (glReadPixels GL_RGBA), 33 = BGRA8 from SDL_RenderReadPixels(ARGB8888) and X window surfaces; xgrab.c tags its ZPixmap BGRA records 33 as well. gzf2_video.py continues to accept both tags (and old all-32 captures via --pix-fmt bgra), checks ffmpeg/ffprobe before indexing, and keeps the final resampled endpoint so a 90-frame 60 fps capture encodes as 90 frames instead of 88.
* vgsp: eng62 - fill missing golden SA entries (slot 34 DRAW_IAB = IR 0x265), ↵Arthur Hanson Rasmusson27 hours
| | | | | | | | | | | | | | | | | | | | default off The golden overlay writes all 55 slot bodies, but the CALL_MME_MACRO(34) DRAW_IAB run targets SA[34]; the client's captured SA table only covered slots 0-11 (c772), so slot 34 resolved to IR 0 (the slot-0 body) and the macro never produced mac=0x22. Add sema_gl_mme_sa_golden_fill (bool, 0): for every slot whose client SA entry is missing/zero and whose golden body exists (kernel/golden-mme-tu104.h golden_mme_tu104_sa[64]), set the SA entry to the golden body's IR entry (slot 34 = 0x265, 75 words) and mark it present. Nonzero client entries are never overwritten. Fill runs in the golden overlay, in the submit path before the stub/call-drop walk, and in the SA re-arm (the release-carrier path); the release path re-fetches and emits the filled 0x11c pairs. New MME-GOLDEN sa-fill/sa-census receipts. c774 proves the fill: `MME-GOLDEN sa-fill slot=34 entry=0x265 (client=missing)`. Enable in params-r1624. Build rc 0; the mac=0x22 validation needs a c772-class release boot.
* vgsp: eng61 - prefer a DRAW_IAB-bearing window in the release save ↵Arthur Hanson Rasmusson27 hours
| | | | | | | | | | | | | | | | | | (diagnostic + robustness) The saved-window release carrier replays the client's held window with the CALL runs kept. Save the raw window after scanning it for the CALL_MME_MACRO(34) DRAW_IAB run (method 0x3910, the 0xA00A0E44 ten-data run); if the saved record already carries it and a later held window does not, keep the saved one (bounded MME-CARRY-SAVE-PREFER receipts). Caveat established from c772: its 728 B window also carries the 0xA00A0E44 slot-34 run at raw[113], so the DRAW_IAB window bytes are not the discriminator; the c772 replay ran 0x33/0x0/0x39 because SA[34]/the golden IR entry was stubbed, not because the window lacked the call. The next lever is the SA[34]/golden-body residency census, not the window choice. Build rc 0; validation pending.
* tools: enable the pack continuation and saved-window release carriers in ↵Arthur Hanson Rasmusson27 hours
| | | | params-r1624 (c772: identity CARRY-FIRE mode=release -> synthetic push 0x6d6d6500 -> REARM gen=5 -> DS 0x84000420)
* vgsp: eng59c - preserve the saved release window across the beef channel ↵Arthur Hanson Rasmusson27 hours
| | | | | | | | | | | | | | | | | | | | | recycle; defer non-ready takes c765/c766: the release carrier saved the held 324/728 B window, then the client re-registered the beef channel before the pack completed. The follow-up's chan_ctx_reset cancelled the saved record unconditionally (consumed=true, valid=false) even though keep_done_across_recycle=1 means the engine context and packed program survive; the pack-completion arm then early-returned and the release never fired. With keep_done_across_recycle=1 the re-register is a client-handle recycle, not a context loss: keep the release record. Cancel it only in the genuine !keep_done wipe path. Also make release_take defer (not consume) on not-armed/grace/pack-not-resident with bounded MME-CARRY-HOLD receipts; only terminal conditions or a failed fire consume. release_rearm now runs unconditionally with the knob on and release_arm gates on pack_done, so the record survives the save->completion gap. Build rc 0; validation pending.
* vgsp: eng59b - do not let the arming launch consume the release carrier; ↵Arthur Hanson Rasmusson27 hours
| | | | | | | | | | | | | | | | | | | | re-arm in the pump The saved-window release carrier was armed inside the pack-completing launch's own build, and the client-first cancel treated that same launch (and its retries) as the next client launch, silently dropping the claim. c762: MME-CARRY-SAVE (win=240 held=68) -> MME-CARRY-ARM mode=release -> the arming launch ran mac=0 (LOAD-ONLY, window dropped, held CALLs still owed) -> no FIRE, no synthetic push, no mac=0x22. Track the arming launch identity (h + push) and keep the claim armed across it; only the MME-PACK-REARM edge (calls actually released), a real consumer, context/handle changes, or a launch error cancels/consumes. Add a pump-side re-arm once pack_done_gen is set, and bounded MME-CARRY-HOLD receipts for every skip. One fire per pack completion, no retries. Build rc 0; validation pending (c762-class boot with sema_gl_mme_pack_release=1).