mirror of
https://github.com/MobileGL-Dev/MobileGL
synced 2026-11-15 22:13:24 +09:00
swung0x48
aba329cc53
Two things land together: the plan and contract draft P6 needs before it starts, and the
working notes that until now existed on exactly one machine.
1. P6's plan and contract draft (neither started; not one line of code)
docs/Disaggregated/P6-SPAWN-PLAN.md the package plan
docs/Disaggregated/P6-CONTRACT-DRAFT.md the contract draft (moves to
MG_Remote/CONTRACT-P6.md when c6 lands)
The three findings that mattered, all written into the documents:
a. P6 is SMALLER than its roadmap cell suggests. The transport primitives are already in
the tree and already tested: SocketDoorbell including hangup detection and the two
lost-wakeup fences (Doorbell.cpp:211-360, four cases in FdPassingTest), SCM_RIGHTS fd
passing, ShmSegment::Adopt, and the SurfaceOp / WindowKind schema already defined in
protocol.fbs. inproc uses a real second shm mapping rather than an alias, and
SessionRings.h:22-28 says that was done so today is not the first time it runs. P6 is
assembly plus a control plane plus a process, not "write a socket transport".
b. The evidence for "P6 is only a transport swap" has EXPIRED. It was bought by P5c, whose
audit found 59 direct memory accesses in a tree that already looked clean. P5e changed
the tree again. So the first package, a6, is a read-only audit that writes no code, and
every contract row that depends on it is marked PENDING a6 rather than decided in
advance.
c. P6 does not get a game running on the phone. ANativeWindow* is meaningless in the child,
and protocol.fbs:186-196's own comment says Android transfers the window out of band -
that band is P12. P6 lands pbuffer / surfaceless / offscreen, which is what HeadlessGL,
the split-equivalent lane and trace replay need, and which is exactly what P6's own exit
gate measures. A real window reaching the server is a named refusal. This gets its own
section because "P6 is done" would otherwise read as "the game runs now".
The contract adds rule G: a role may not name a process-local handle. It extends P5c's
rule E (a role may not name the other role's memory) from memory to identity - EGLDisplay /
EGLSurface / EGLContext / ANativeWindow* / fd number / pid / mapped address either cross as
a token this contract defines or they do not cross, and a descriptor crosses only through
SCM_RIGHTS, where the kernel renumbers it.
What P5e left for P6 gets its own section. The latch semantics are already designed
(ARCHITECTURE.md:504) and are copied unchanged. What is new is that after run-ahead the
client no longer waits while the peer process can DIE: the client holds records that were
published and will never be applied, and Android's freezer suspends the child without
closing anything. So slow and dead must be distinguishable WITHOUT a timeout threshold.
That is P6's only new design; everything else is carriage. It shares a predicate with E1's
outstanding re-specification (ID-122), and the two should be designed together.
Two gates carried over from P5e's lessons: G2 requires integration-spawn's test-name set to
match integration-split's name for name, because a differing set means the lane is quietly
running less; and the arm-proof gate requires every entry to record the child pid and
transport=spawn in its OWN private log - ID-124 established that this kind of false green
really happens, and a spawn lane that actually ran monolith would pass every other gate.
S2's shape must be settled before it is written, and the document says why: E1 is the
cautionary case.
2. The working notes move into the repository (docs/Disaggregated/notes/, 415 .md files)
ROADMAP / CURRENT_STAGE_PROGRESS / MEASUREMENTS cite ruling numbers, audit line numbers and
the provenance of gate figures from ~/w7/notes/, a directory that exists on one machine and
is under no version control. A record cited hundreds of times that lives only locally is not
a record, so it moves in whole, with its directory structure intact.
Only .md moves. Scripts, run logs, census and gate result JSON, patches, APKs and nm dumps
stay where they are: they are evidence DATA rather than documents - large, regenerated per
run, and mostly carrying absolute paths and device serials that mean something only on the
machine that produced them. The mapping and this split are written in
docs/Disaggregated/notes/README.md.
Two exceptions are recorded there too: P6's BRIEF has been promoted to a first-class
document and keeps no copy under notes/, so the two cannot drift apart; and recovered/ holds
material salvaged from failed workflow runs, which may duplicate the like-named phase
directories and is kept because a few of those were the only complete version at the time.
CI's citation lint takes docs/Disaggregated/*.md only (non-recursive), and notes/ is
deliberately outside it: those notes' file:line citations were written against their own
code heads, and resolving them against today's HEAD would fail wholesale - which is not an
error, it is their correct state as a historical record. To check one, use the revision it
declares (--rev).
3. Inconsistencies fixed in passing
- README.md's status line still said P5e was in progress while the stage table already said
closed.
- CURRENT_STAGE_PROGRESS's next-step item 1 still listed the exit gate as pending, though
(a) and (b) were run in the previous commit; rewritten to closed plus the one item that
actually remains (E1).
- ROADMAP's P6 row still had the pre-phase plan in three of its cells; it now carries the
package order, the scope boundary and the two new gates.
Checked with check_doc_citations.py: 125 citations across docs/Disaggregated/*.md, 0 problems.
3.2 KiB
3.2 KiB
P5b named blit migration
Commit 31b26a440de4d52c1afb746ed934247da8b8b145, branch p5b/blit-codex, base 9606466a; independent tree /home/swung/w7/p5b-blit-codex.
The client emit table now lowers BlitNamedFramebuffer through a scoped client-shadow read/draw binding override. It revalidates the existing classified fields, emits the original two handles/rectangles/mask/filter in the existing MGPBlit row, waits for server apply, then restores both bindings. BindingSlot versions make the following ordinary verb republish restored bindings. The server keeps using its existing bound backend entry point; no driver call runs on the client, and no pointer or extra side channel was added. Name zero uses the existing default-framebuffer handle. CONTRACT-P5B §6 item 13 records the integrator-approved ruling and its retirement when the lockstep barrier/process-shared access disappears.
Only split production sources changed. Pull G1 was not remeasured locally; the integrator owns the merged-head four-flavor gate. Slot partition is now A=2/B=49/C=20. Named clears are unchanged.
Directed validation
- Split configure and full default ALL build succeeded at -j8; CTestTestfile.cmake exists. Logs
/home/swung/w7/p5b-blit-codex-{config-split,build-split,build-driver}.log. - Four new split cases all executed and passed: two cases × DirectGLES/DirectVulkan. They check separately unbound source/destination, preserved public read/draw names, an immediate ordinary clear before another bind, following ordinary blit, and default FBO as source/destination.
- RemoteEmitTable: 15/15 pass. Combined targeted CTest: 23 selected = 19 executed pass + four deliberately skipped monolith registrations of the split-only scenarios. Those skips are not counted as split execution. Log
p5b-blit-codex-targeted.log. - Dynamic retrace: exactly four selected, stock
/home/swung/w7/retrace_gate.py,MOBILEGL_TRANSPORT=inproc, default SEG_STAGE=32 MiB. No adb, LFS fetch, repeated full gate or adversarial review.
| Trace | Backend | Result / next first blocker |
|---|---|---|
| improved-transparency-minecraft-26.3 | DirectVulkan | pass, SSIM 0.999914064 (threshold 0.995), zero private Fatal |
| minecraft-1.21.4-fabric-iris-bsl-in-world | DirectVulkan | pass, SSIM 0.997324199 (threshold 0.99), zero private Fatal |
| improved-transparency-minecraft-26.3 | DirectGLES | named blit crossed; Fatal{RingOverrun, "SEG_STAGE"}: 134217728-byte blob exceeds 33554432-byte segment |
| minecraft-1.21.4-fabric-iris-bsl-in-world | DirectGLES | named blit crossed; Fatal{UnmigratedEmulation, "generate-mipmap-storage"} |
Trace evidence: /home/swung/w7/p5b-blit-codex-traces.log, /home/swung/w7/retrace-out/p5b-blit-codex/summary.json, and per-case/backend output/mobilegl.log, result.json, images and outer logs below that output root. The trace fixtures were copied from hydrated pipe files for the run and restored to their original tracked pointers before commit.
The integrator owns a separate larger-stage improved-transparency run; it is not claimed here. The follow-up mip-storage fix is a separate commit/report. git diff --check clean, committer Swung0x48, no trailers, submodule links off at commit.