mirror of
https://github.com/MobileGL-Dev/MobileGL
synced 2026-11-16 06:23:23 +09:00
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.
61 lines
3.5 KiB
Markdown
61 lines
3.5 KiB
Markdown
# Wave 3 census — the strict lane at `3c13fa4b` (pa + mv + ID-124 merged)
|
|
|
|
Harness: `strict_census3.py`, which takes each entry's OWN command and environment from
|
|
`ctest --show-only=json-v1` and layers only `MOBILEGL_IPC_STRICT_ERRORS=1` and a private
|
|
`MOBILEGL_LOG_FILE_PATH` on top, last. The two earlier harnesses each produced a table that looked
|
|
complete and was not: v1 was defeated by lane-pinned log paths, v2 by re-running 14 of 109 entries
|
|
under an environment their lane does not use.
|
|
|
|
## The table
|
|
|
|
180 lane entries. 24 green, 156 red.
|
|
|
|
| marker | entries | admitted by | owner |
|
|
|---|---|---|---|
|
|
| `GetFramebufferBindingSlot@ReadPixels` | 113 | ID-116 disjunct 1 (ReadPixels is statically barriered) | trails to P8/P9 |
|
|
| `GetBufferBindingSlot@DrawArrays` | 18 | ID-125 disjunct 2 (retires P8 / P9 / P13) | P8 |
|
|
| `GetTransformFeedbackProgram@DrawArrays` | 11 | ID-125 disjunct 2, and ID-128 disjunct 3 | P3b/P4b |
|
|
| `GetTextureObject@CopyImageSubData` | 6 | ID-125 disjunct 2; ID-118 also makes disjunct 1 hold | P7 |
|
|
| `ValidateProgramName@ShaderStorageBlockBinding` | 2 | ID-125 disjunct 2 (retires P9) | P9 |
|
|
| `GetBoundVertexArray@DrawArrays` | 2 | **ID-128 disjunct 3 only** | P8 (client arrays) |
|
|
| `GetTextureUnitObject@CopyTexImage2D` | 2 | ID-116 disjunct 1 | trails |
|
|
| `GetFramebufferBindingSlot@Clear` (DirectVulkan) | 2 | ID-125 disjunct 2 on the Magma side | P7 |
|
|
|
|
**`GetProgramForDraw@DrawArrays` and `GetProgramForDispatch@DispatchCompute` are gone.** They were
|
|
62 and 7 at the wave's base and they were the per-draw pull that kept every draw barriered.
|
|
|
|
## Two rows that the wave created, and both were predicted
|
|
|
|
- **`GetBufferBindingSlot@DrawArrays`, 18 entries, all in `MultiDrawTierIndirect` and
|
|
`MultiDrawTierMultiIndirect`.** Package `mv` NAMED this in its report as a latent row before it
|
|
could fire: `BoundDrawIndirectBufferId`'s `GetBufferBindingSlot(DrawIndirect)`, which "would
|
|
surface as `GetBufferBindingSlot@DrawArrays` if an indirect tier were ever forced under strict".
|
|
It then gated the indirect tiers, which forced them. The field retires in P8 (`FieldOwnership.def:78`),
|
|
so it is admitted, not owed. A latent row named and then made visible in the same package is the
|
|
outcome you want.
|
|
- **`GetFramebufferBindingSlot@ReadPixels` grew from 19 to 113.** Unmasking: entries that used to
|
|
die on the program row now get as far as their readback.
|
|
|
|
## The rule is now complete against this table
|
|
|
|
Three disjuncts, and every row above is covered:
|
|
|
|
1. the verb's wire op is statically barriered (ID-116);
|
|
2. the field's retiring phase does not name P5e (ID-125);
|
|
3. the record was barriered by ESCALATION rather than statically — `wireSaysBarriered && waitClass == kWaitNone` (ID-128).
|
|
|
|
Disjunct 3 exists because of exactly two entries, both `ClientVertexArrayScenario.*`, and it is the
|
|
principled one rather than a patch: escalation happens only for XFB-active and client-array draws,
|
|
and the contract puts both outside this phase.
|
|
|
|
**Hard green is therefore a checkable number: 180 of 180, eight rows reporting `Admitted{`, zero
|
|
reporting `Fatal{`.** Not an argument.
|
|
|
|
## What is NOT in this table
|
|
|
|
The census measures first faults under the strict knob. It says nothing about whether run-ahead is
|
|
correct, only about whether any record still reads client memory in a way P5e owes. The negative
|
|
controls, the red-once re-runs and the device exit are separate gates (`FLIP-CHECKLIST.md` phases C
|
|
to E), and BRIEF §3 item 5's evidence form had to be re-sequenced because every candidate was red
|
|
before the revert (ID-121).
|