mirror of
https://github.com/MobileGL-Dev/MobileGL
synced 2026-11-07 18:13:23 +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.
48 lines
2.6 KiB
Markdown
48 lines
2.6 KiB
Markdown
# 工作笔记（原 `~/w7/notes/`）
|
||
|
||
这一层是 MGPipe 各阶段的**工作笔记原件**：包计划（`BRIEF-*.md`）、契约草稿、集成者逐条裁定
|
||
（`INTEGRATOR-DECISIONS-*.md`）、只读审计、普查、设备记录、包任务书（`TASK-*.md`）与阶段报告。
|
||
|
||
它们此前只存在于一台机器的 `~/w7/notes/` 下。上层那几份文档（`ROADMAP.md`、
|
||
`CURRENT_STAGE_PROGRESS.md`、`MEASUREMENTS.md` …）**大量引用它们**——裁定编号、审计行号、
|
||
逐门数字的出处几乎全在这里。一份引用了几百次、却只存在于本地未跟踪目录的记录，等于没有记录。
|
||
所以整体移进仓库。
|
||
|
||
## 路径映射
|
||
|
||
```
|
||
~/w7/notes/<phase>/<file>.md → docs/Disaggregated/notes/<phase>/<file>.md
|
||
```
|
||
|
||
上层文档里凡写作 `~/w7/notes/...` 的 `.md` 引用，都按这条规则读。
|
||
|
||
## 移进来的是什么，没移的是什么
|
||
|
||
| | |
|
||
|---|---|
|
||
| **移进来了** | 全部 `.md`，415 份，约 11 MB，目录结构原样保留 |
|
||
| **没有移** | 脚本（`.sh` / `.py`）、运行日志（`.log` / `.out` / `.err`）、普查与门的结果数据（`.json` / `.txt` / `.tsv`）、补丁、APK 与 `.idsig`、`nm` 转储 |
|
||
|
||
没移的那些仍在 `~/w7/notes/` 与各构建树下。它们是**证据数据**而不是文档：体积大、随每次运行
|
||
重新产生、且多数只在产生它的那台机器上有意义（绝对路径、设备序列号、构建目录）。上层文档引用
|
||
它们时给的是路径，不是内容。
|
||
|
||
## 两个需要知道的例外
|
||
|
||
1. **P6 的包计划已提升为正式文档**：原 `~/w7/notes/p6/BRIEF-P6.md` 现在是
|
||
[`../P6-SPAWN-PLAN.md`](../P6-SPAWN-PLAN.md)，本目录不再保留副本，避免两份同源文档各自漂移。
|
||
契约草稿同理，见 [`../P6-CONTRACT-DRAFT.md`](../P6-CONTRACT-DRAFT.md)。
|
||
2. **`recovered/`** 是从失败的 workflow 运行里捞回来的材料（`wf1`…`wf5`），与同名阶段目录
|
||
**可能重复**，保留是因为其中几份是当时唯一的完整版本。查阶段记录请先看阶段目录。
|
||
|
||
## 不受 citation lint 管
|
||
|
||
CI 的文档引用 lint 只吃 `docs/Disaggregated/*.md`（非递归，`.github/workflows/test.yml`），
|
||
**本目录不在其中，这是有意的**：这些笔记的 `file:line` 是写在各自当时的代码头上的，拿今天的
|
||
HEAD 去解析必然大面积失败，而那不是错误——那是它们作为历史记录的正确状态。要核对某份笔记的
|
||
引用，用它自己声明的那个 revision：
|
||
|
||
```bash
|
||
python3 scripts/check_doc_citations.py --rev <当时的头> docs/Disaggregated/notes/<phase>/<file>.md
|
||
```
|