| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(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.
|
| |
|
|
| |
deterministic (c772), slot-34/SA[34] settled (0x265), call order is the blocker; eng64 chains the release behind the pack carrier; STATE-CURRENT snapshot
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(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.
|
| |
|
|
| |
params-r1624 (c772: identity CARRY-FIRE mode=release -> synthetic push 0x6d6d6500 -> REARM gen=5 -> DS 0x84000420)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(default off)
When a 324 B draw window holds its CALL runs while the 2799-word pack is
incomplete, the pack can complete later (X lane or a 728 B window) but the
next client launch that would release the held calls is a per-frame lottery
(c756: MME-CALL-HOLD 18, pack complete, no next launch -> no REARM/mac=0x22).
Save the held window at MME-CALL-HOLD (raw pre-relocation stream + the
launch capture fields) into module memory. When the pack is complete and
resident and no client launch consumes the release within
sema_gl_mme_pack_release_ms, re-submit the saved capture through the normal
fill/build path with the held CALL runs KEPT (mme_hold_calls=false), no
prelude emission, and gr_synthetic/no guest release. The released
CALL(34) runs DRAW_IAB against the resident pack, the shape c716 proved.
New: sema_gl_mme_pack_release (bool, 0) / _ms (uint, 100); MME-CARRY-SAVE /
ARM/FIRE/COMPLETE/CANCEL/ABORT mode=release receipts. Beef-only, one fire per
pack completion, fail-closed on context/handle changes or launch errors. The
existing pack-continuation carrier is unchanged with its knob off.
Build rc 0; validation pending.
|
| |
|
|
| |
stage TYPE/COUNT before the address pairs; DS A/B)
|
| |
|
|
| |
(st0=st1=020a0481; DS 0x84000420, two boots); draw-issue mac=0x22 and stores remain; STATE-CURRENT snapshot
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
image, and harden the author window-head decode
- gsp_phys_booter.c: after authoring the VTG SPH at family+0x900, scan the
patched 3D window for its own 0x2054 slot-1 pair and rewrite an operand
whose low 12 bits are 0x600/0x300 (client family VA or pair-cache shadow
line) to <page>|0x900. The window's own later pair otherwise overwrites
the synthesized prelude j1 and the DS validates the client's SASS page
(c743: DS-IMAGE st1=0b0b7208). New SPH-SLOT1-REWRITE / SPH-SLOT1 receipts.
- gsp_phys_booter.c: reject an inline VTG candidate whose IMAP word (w6,
offset 24) is zero; fall back to the builtin image. A 640 B w6=0 record
authored a zero-map SPH and the DS went to the FECS/PRI sentinel
(c749 fam 0x4350000: ds 80000000->badf1201).
- gsp_sema_service.c: the DDX ring-head decode scans past zero-payload
and unreadable entries within the 8-entry bound instead of stopping
(c746: the ring head is a zero dummy and the C36F release sits later);
it still never fabricates a payload.
Validation: c749 is the first boot with DS-IMAGE st0=st1=020a0481
(code ff007321, the authored VSA/VSB image), a clean slot-1 rewrite
(old=0x01e00300 new=0x01e00900), beef MME-PACK-REARM, and the DS latch
reduced from 86040626 to 84000420; stores are still 0 and the DRAW_IAB
macro is the next gap.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
decode, MME pack carrier, and the pump atomic-sleep hoist
- gsp_phys_booter.c: sema_gl_sph_vtg_auth (default 1) authors the client's
live VTG SPH image at family+0x900 and binds VSA/VSB there; new
SPH-AUTHOR / SPH-ALIAS-auth receipts and a DS-IMAGE stage census at the
DS latch (stage-start w0 + code word through the pair cache).
- gsp_phys_booter.c: sema_gl_mme_pack_carry (default 0) + _ms (default 100)
host-initiated windowless continuation carrier for a split MME pack;
MME-CARRY-ARM/FIRE/COMPLETE/CANCEL/ABORT receipts, beef-only, bounded.
- gsp_sema_service.c: sema_ddx_tracker_auth (default 0) ring-head decode
for the DDX channel when the USERD is missing/reset (guest-authored
C36F release applied verbatim); sema_gr_scan_top default raised to
0x300000000 for the 12 GiB campaign guest.
- gsp_sema_service.c: hoist the r707e VAS candidate verify out of
svc.chan_lock (its vfio_dma_rw path can sleep) and add in_atomic guards
to svc_read/svc_write; fixes the gsp-sema-svc "scheduling while atomic"
pump stall that lost the marked draw-window launch.
- tools: enable sema_ddx_tracker_auth=1 in params-r1624; use timeout -k in
the guest GL/GZDoom wrappers so a wedged GPU wait cannot hang a cycle.
Validation: c741/c743 boots (VTG author byte readback, cross-lane and beef
pack completion + REARM, DS-IMAGE census) and the c743 DS-FAST chain; A/B
for the carrier and the tracker decode is still open.
|
| |
|
|
| |
landed; draw macro executes, store pending)
|
| |
|
|
| |
landed; draw macro executes, store pending)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
draw-synth windows, preserve the last beef push, and default the DS stage-image A/B safe
- gsp_phys_booter.c: the synthesized SPH-BIND stage-block guard
double-counted the already-emitted raster words (101 > 96), silently
skipping j0/j2/j4/j5; pre=29 -> pre=84 and the DS stage VAs populate.
Add the SPH-BIND-STAGE-SKIP receipt.
- gsp_sema_service.c: sema_gl_win_rt0_admit (default 1) admits a beef
draw-synth window whose FIRST colour-target write is a usable
surface-class bind (RT0-FIRST-MISS witness); preserve the most recent
beef push (>=256 B) for the gsp-phys-last-push debugfs dump; skip the
non-RAM windows in the linear ring scan; fix the MME shadow-RAM index
shift to (mthd >> 2) & 0xfff.
- gsp_phys_booter.c: sema_gl_sph_vtg600 (default 0) and
sema_gl_sph_vtg_j1 (default 0) are the stage-image A/B: binding
family+0x600 poisons the DS (the engine-visible alias shadow there is
the client's SASS upload), so keep the historical +0x900 zero page
until a real VTG SPH is authored at an engine-visible VA.
- tools/guest-diag/params-r1624.txt: enable sema_gl_win_rt0_admit.
- wiki/Project-Status.md: 2026-11-15 status (MME chain completes and
executes DRAW_IAB; DS stage image is the named gate).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
auto-dropped 0x22c run (eng50)
The SPH-BIND prelude emitted '0x22c <- 0x800', which is on
win_drop_auto_match's drop list: the patch pass removed exactly 2 words, so
kept=29/31, on==nfin failed and the WHOLE prelude was discarded on every beef
window -> VSA/TCS/GS unbound -> DS latch a2040a04 (stage[1] fetch VA
0x01df0300) -> DRAW_IAB (mac=0x22) never rasterized. Fix: omit the
auto-dropped run from the synthesized prelude (knob-consistent) + a WIN-DROP
diagnostic. Built (srcversion 2D8F375AB343FC73EA26286); end-to-end validation
blocked in-window (c704-6: draw-synth RT-guard refusal + WEDGE-REARM rc=-110
before SPH-BIND was reached).
|
| |
|
|
|
|
|
|
|
| |
Follows the same any-channel rule as sema_mme_prelude_cap_any and emits
'sema-mme-xscan: ... hits=0' when a push yields no MME-family ops (scan
coverage evidence). c693: X-lane pushes (0x120010000/0x1200a0000/0x120010004)
show hits=0 - the indirect-mode X pushes carry no MME setup runs, so the
prelude feed has nothing; the MME setup runs likely ride the beef ring (whose
entries the walk skips as garbage in the read lottery).
|
| |
|
|
| |
prelude feed for the indirect replay chain; A/B pending)
|
| |
|
|
|
|
|
|
|
|
|
| |
(sema_mme_prelude_cap_any, default 0) (eng48)
The X DDX indirect lane (h=0x1000013) replays its 3D windows verbatim but
never builds the MME pack because svc_mme_prelude_capture rejects every
non-beef channel, so pl_n=0 and emit_prelude skips. c487 proved the X lane
emits a 2799-word pack when pl_n>0. New bool sema_mme_prelude_cap_any=1
bypasses the beef gate and feeds the same signature-deduped capture;
default 0 keeps legacy beef-only behaviour bit-for-bit. Validation pending.
|
| |
|
|
| |
alias for the post-REARM macro path; A/B pending)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
(sema_gl_mme_cb_alias, default 0) (eng45)
Macro 57 (LOAD_CONSTANT_BUFFER) reads the 0x7000-byte fixed CB at
seed-shadow +0x5000, but only the single seed page was mapped (the
pre-existing fixed-CB+0x4000 class), producing FAULT_PTE VIRT_READ at
0x0_015a5000 11 ms after the released calls (post-REARM). The alias maps a
contiguous 7-page region in the scratch PT pool (page 0 = CB image/MVP;
unservable tail = dummy zero page), wired into the scratch-0x18 and d19
seed paths, logged MME-CB-ALIAS. Safety-validated c654 (alias exercised,
0 MMU faults, 0 badf1201, 0 poison all boot); the beef macro chain was not
reproduced in-window, so end-to-end validation is pending.
|
| |
|
|
| |
keep the MME pack completion record + cursor across the beef owner channel re-register so the first post-recycle prelude launch is non-emitting and MME-PACK-REARM fires; A/B pending)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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).
|
| |
|
|
| |
globally (pack_done_gen/ch) so the post-completion call release fires for cross-lane completions (c552: part 1 on X, completion on beef -> pack_done_h withheld, REARM unreachable); restart the owner-less wedged cursor (poff==maxa && done_h==0) so a later window can re-emit the deterministic golden image (validation pending)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
context-reset invalidation (eng40, validation pending)
After the multi-part beef pack completes (2799/2799; keep_gen=1 works), the
prelude generation drifts and the pack branch refuses re-emission (poff==maxa),
so calls stay held forever (pcv=0, shadow draws 0, wrote=0). This adds:
(1) per-channel contiguous-load accounting + pack_done_h so the completion is
remembered for the loaded channel; (2) an MME-PACK-REARM call release when a
completed pack's channel launches again; (3) gsp_phys_gr_mme_chan_ctx_reset(h)
invalidation on context wipes/channel re-registers (the client recycles the
beef channel between pushes, c496), shown firing safely. Validation: the fix
was not yet observed completing on a green window with a same-incarnation draw;
committed for reproducibility per house style.
|
| |
|
|
| |
multi-part pack restarts on prelude-generation churn between parts; keep the packed cursor across churn when golden_force=1; A/B pending)
|
| |
|
|
| |
SET_REPORT_SEMAPHORE/SET_NOTIFY targets to the mapped module scratch slot (sema_gl_report_sem_scratch, default 1); add sema_gl_mme_pack_keep_gen (default 0) to keep the packed-part cursor across deterministic-image generation changes (eng39)
|
| |
|
|
| |
(macro-driven), push rescues land, draw-state push reaches the engine; MME multi-part completion is the wall; STATE-CURRENT snapshot
|
| |
|
|
| |
let partial MME pack parts keep their windows so the multi-part beef program can complete and promote live_gen; A/B pending)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
sema_gl_mme_partial_keep_window (default 0 = legacy) (eng36/eng37)
The load-only carrier gate turns every 3D window launch windowless while the
packed MME program generation is not latched+live. A launch that emits only a
PART of the packed program (block room exhausted) cannot make the program
resident, so dropping its window also discards the draw's state and defers the
completion to an unrelated later push, where it dies (GP_GET-frozen /
MISSING_MACRO_DATA) and the generation never promotes.
New knob sema_gl_mme_partial_keep_window (default 0 = legacy drop-everything):
when set, only a launch that emits the FINAL part of the pack stays a
windowless carrier; partial-part launches keep their window in the calls-held
shape so client state accumulates and the completing carrier can promote the
generation and let the next window run real calls.
|
| |
|
|
| |
targets RT0 - MRT_SELECT=0 in CLEAR_SURFACE 0x3c - while the window binds RT1; bind RT0 to the same surface so the clear has a target)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
window-0 shadow instead of leaving the QMD pointer at an unmapped guest VA (eng33)
The client's MME-expanded draw builds a QMD whose program page (qmd[48])
classifies CODESRC-SUSPECT (empty-page): the engine's GPCCLIENT_GCC I-fetch
then read the guest VA above every engine-PDB window, raised FAULT_PDE and
the FIFO parked for the rest of the boot (the TSG re-arm cannot revive a
parked PBDMA). c361-c368 receipts.
With gsp_phys_gr_codesrc_reloc=1 (default) the builder copies the page into
the window-0 shadow (empty sources only; PTE/module pages are never
republished), overlays the client's own known-good SPH+SASS stage image at
the original QMD program offset (gsp_sema_gl_prog_img, stage-typed from the
section bind; truncated at a 128-bit boundary with a terminal EXIT when the
image is larger than the remaining page), and the existing QMD w48/49 +
prefetch rewrite publishes the shadow VA. If the shadow mapping cannot be
installed the page stays unmapped and the existing refusal drops the launch,
so an unmapped QMD program pointer is never published. 0 restores the old
guest-VA behaviour for a one-flip A/B.
Validation (c373, params-r1624): 31 CODESRC-RELOC events (img_len=384,
off=0xb00, 0 truncations), 51 GR LAUNCH submitted, 11 MME-FAST end
events=3, 79 FETCH-WIT with GP_GET advancing engine-fetched, 0 FAULT_PDE,
0 vgsp-fault, 0 WEDGE-REARM/PARK-RECOVER; work_gr backend_ok=35 fault=0.
The draws still write nothing (NOWRITE, no clear run in the emitted
window), so px0 stays 0 - the store wall is unchanged and is the next
target.
|