swung0x48/MobileGL
1
0
Fork 0
mirror of https://github.com/MobileGL-Dev/MobileGL synced 2026-11-07 10:03:23 +09:00
Code Issues Packages Projects Releases Wiki Activity
Files
6946ff3a5ca1825c713285faf2ea18fd2b5403a7
MobileGL/docs/Disaggregated/notes
T
History
swung0x48 6946ff3a5c [Docs] (Anland): refresh the handoff to the post-P14 landed state 
The document still described the state before the state-ownership work
landed: it called the unified server design unfinished, listed the
KernelSU grant as unsolved, said the directory bind had not taken effect,
and presented MobileGLAppsService plus the per-app fork worker as pending
drafts. None of that is true now.

Rewritten against the current tree and the device:

- header: architecture landed per the user's correction, acceptance still
  open; the rejected fork-worker/AppsService path is removed and the
  unified server lives in the MobileGL library (design 11-state-ownership,
  commits d52c031c / 4ed1c9ce / 5c6399e2 / ff212061 / 5a0f13fd, plus the
  landed 6fb880cd / ebc552a0 that used to be listed as uncommitted)
- MobileGL: HEAD moved to 5a0f13fd; the state-ownership section now records
  what S1-S6 landed and the debts that remain (process-level unit shadows,
  g_backendContextGeneration, per-record ContextSlot, the glIsBuffer probe,
  the window half of pbuffer->window)
- anland: 2ffa1f5 and 33e496c pushed; the draft inventory is now a landed
  inventory plus the three uncommitted KWin-acceptance fixes
- device: KernelSU grant resolved (reinstall changed the uid to 10270), the
  clone restarted with the directory bind effective, the 5a0f13fd APK
  serving @anland-mobilegl with six completed client sessions, and the
  client library installed with a stale build stamp
- new: concurrency warning (parallel sessions have overwritten the dist and
  the source tar), the current desktop-session.service failure state, and a
  rewritten continuation order

Verified: doc citations resolve (scripts/check_doc_citations.py), device
facts checked against HA27Q3LQ at refresh time.
2026-10-01 20:41:54 -04:00
..
anland
[Docs] (Anland): refresh the handoff to the post-P14 landed state
2026-10-01 20:41:54 -04:00
handoff
[docs] (P7): ID-P7-60/61/62 - the codex closeout fixes, the spawn cold-start heartbeat, and gate 3's nondeterministic-monolith ruling; window 2 reads gate 5 PASS
2026-09-23 19:34:55 -04:00
p0
[Docs] (Disaggregated): the four index documents keep only summaries, and every phase's detail lives in its own notes/<phase>/README.md
2026-09-24 22:21:09 +00:00
p1
[Docs] (Disaggregated): the four index documents keep only summaries, and every phase's detail lives in its own notes/<phase>/README.md
2026-09-24 22:21:09 +00:00
p2
[Docs] (Disaggregated): the four index documents keep only summaries, and every phase's detail lives in its own notes/<phase>/README.md
2026-09-24 22:21:09 +00:00
p3a
[Docs] (Disaggregated): the four index documents keep only summaries, and every phase's detail lives in its own notes/<phase>/README.md
2026-09-24 22:21:09 +00:00
p4a
[Docs] (Disaggregated): the four index documents keep only summaries, and every phase's detail lives in its own notes/<phase>/README.md
2026-09-24 22:21:09 +00:00
p5
[Docs] (Disaggregated): the four index documents keep only summaries, and every phase's detail lives in its own notes/<phase>/README.md
2026-09-24 22:21:09 +00:00
p5b
[Docs] (Disaggregated): the four index documents keep only summaries, and every phase's detail lives in its own notes/<phase>/README.md
2026-09-24 22:21:09 +00:00
p5c
[Docs] (Disaggregated): the four index documents keep only summaries, and every phase's detail lives in its own notes/<phase>/README.md
2026-09-24 22:21:09 +00:00
p5d
[Docs] (Disaggregated): the four index documents keep only summaries, and every phase's detail lives in its own notes/<phase>/README.md
2026-09-24 22:21:09 +00:00
p5e
[Docs] (Disaggregated): the four index documents keep only summaries, and every phase's detail lives in its own notes/<phase>/README.md
2026-09-24 22:21:09 +00:00
p5f
[Docs] (Disaggregated): the four index documents keep only summaries, and every phase's detail lives in its own notes/<phase>/README.md
2026-09-24 22:21:09 +00:00
p6
[Docs] (Disaggregated): the four index documents keep only summaries, and every phase's detail lives in its own notes/<phase>/README.md
2026-09-24 22:21:09 +00:00
p7
[Docs] (P9 W2): W2-REMINT - no pull protocol, the census, the coverage matrix and the red-once record; design/04 8.4, the P5c/P5e contract amendments, open question 2 and the P7 census attribution
2026-09-29 03:24:03 -04:00
p8
[Docs] (P8): close the phase - ruling ID-P8-19 (the exit device check and the P12 cross-host rerun), the P8 README and PLAN, the roadmap row and header, MEASUREMENTS row 19, the status page and the last debt
2026-09-30 08:25:38 -04:00
p9
[Docs] (P11): rulings ID-P11-1..9 with the integration gate, A-DEVICE (T0 is GO from the app domain on both backends; adoption buys RSS not frame time on the Adreno; split T2 costs RSS and p99), the debts the dev merge closes and the ones P11 hands on, and W2-REMINT marking the monolith re-mint fixed
2026-09-29 08:03:09 -04:00
p05
[Docs] (Disaggregated): the four index documents keep only summaries, and every phase's detail lives in its own notes/<phase>/README.md
2026-09-24 22:21:09 +00:00
p10
[Docs] (P10): close the phase - CONTRACT-P10 sections 2-3, rulings ID-P10-1..14 with the integration gate, C-MEASUREMENTS (device fence bench, loopback credit 1/2/3, the retrace round-trip census), the roadmap row, the debts P10 hands on, design/09, the phase README and the status page
2026-09-29 05:29:00 -04:00
p11
[Docs] (P11): ruling ID-P11-20 - the closing head's gate, lanes and retrace numbers
2026-09-29 21:13:12 -04:00
p12
[Docs] (P12): the FCL fork's keep-running setting is committed and pushed
2026-09-29 01:10:19 -04:00
p13
[Docs] (Disaggregated): the four index documents keep only summaries, and every phase's detail lives in its own notes/<phase>/README.md
2026-09-24 22:21:09 +00:00
p34b
[Docs] (Disaggregated): the four index documents keep only summaries, and every phase's detail lives in its own notes/<phase>/README.md
2026-09-24 22:21:09 +00:00
p65
[Docs] (Disaggregated): the four index documents keep only summaries, and every phase's detail lives in its own notes/<phase>/README.md
2026-09-24 22:21:09 +00:00
perf-five-arm-20260928
[Docs] (P12): exit gate (b) passes - a WSL client replays the in-world trace over Wi-Fi TCP at ssim 0.999883; the load frame is bandwidth-bound, the steady state is latency-bound
2026-09-28 23:22:06 -04:00
recovered
[Docs] (Disaggregated): the four index documents keep only summaries, and every phase's detail lives in its own notes/<phase>/README.md
2026-09-24 22:21:09 +00:00
DEBTS.md
[Fix] (MG_Remote, P11 T0): the T0 POST also checks what the CPU writes through the held lock after the import and its first GPU use, in both directions - Mali-G1-Ultra passed the old single round (the import cleans the CPU cache) while its GPU saw 0/1024 post-import words, so T0 was granted and create-indirect-in-world-align1024 x Magma lost every Flywheel object on inproc/spawn (0.867/0.848); it now fails there and runs T2 (0.999984), and the Redmi passes both rounds and keeps T0
2026-09-30 10:21:46 -04:00
OPEN-QUESTIONS.md
[Fix] (MG_Remote, P11 T0): the T0 POST also checks what the CPU writes through the held lock after the import and its first GPU use, in both directions - Mali-G1-Ultra passed the old single round (the import cleans the CPU cache) while its GPU saw 0/1024 post-import words, so T0 was granted and create-indirect-in-world-align1024 x Magma lost every Flywheel object on inproc/spawn (0.867/0.848); it now fails there and runs T2 (0.999984), and the Redmi passes both rounds and keeps T0
2026-09-30 10:21:46 -04:00
README.md
[Docs] (Anland): research note - what MobileGL and Anland would each need for MobileGL to render Anland's Linux apps (glibc split client in the container, bionic render server, native AHB ingress into waylandbridge), with the two source-audit reports, their briefs and the notes index entry
2026-09-30 11:57:57 -04:00

README.md

阶段笔记（notes）

这一层放各阶段的全部细节：每个阶段一个目录，目录里的 README.md 是该阶段的汇总（摘要、阶段表原行、逐门实测、落地形状、当时的进度页），其余文件是那个阶段的原始工作笔记——包计划（BRIEF-*.md / TASK-*.md）、契约草稿、集成者逐条裁定（INTEGRATOR-DECISIONS-*.md）、只读审计与普查、包报告、设备记录与证据。顶层的索引（../ROADMAP.md、../MEASUREMENTS.md、../CURRENT_STAGE_PROGRESS.md）只留一句话并链到这里；不属于某个阶段的设计正文在 ../design/，上手与参考在 ../guide/。

按阶段

阶段 汇总 重要文件
P0 卫生、度量、门、骨架 p0/ BRIEF-P0.md、p0-device-findings.md
P0.5 值头与制品头 p05/ BRIEF-P05.md、p05-results/
P1 PipeInputs + verify p1/ BRIEF-P1.md、P1-LANE-FINDINGS.md
P2 渲染状态 CSO p2/ BRIEF-P2.md、INTEGRATOR-DECISIONS.md、ab/、bench/
P3a 句柄 wave 1 p3a/ BRIEF-P3A.md、INTEGRATOR-DECISIONS.md
P4a 句柄 wave 2 p4a/ BRIEF-P4A.md、INTEGRATOR-DECISIONS.md、ab-redmi/
P5 传输 + inproc p5/ BRIEF-P5.md、PACKAGE-PREAMBLE.md、p5-results/
P5b verb 迁移 p5b/ BRIEF-P5B.md、p5b-results/p5b-close-codex-review.md
P5c 共享内存读点归零 p5c/ p5c-audit-v1.md
P5d inproc 性能 p5d/ P5D-INPROC-PERFORMANCE.md（报告）、RESULTS-P5D-R3.md
P5e run-ahead p5e/ P5E-RUNAHEAD.md（报告）、INTEGRATOR-DECISIONS-P5E.md（ID-80..136）、TASK-*.md
P5f 一切状态上 wire p5f/ P5F-WIRE-COMPLETENESS.md（计划）、close-report.md、magma-runahead.md、HANDOFF-CI-INPROC-20260920.md
P6 spawn transport p6/ P6-SPAWN-PLAN.md、P6-CONTRACT-DRAFT.md、P6-ENDSTATE-REVIEW.md、a6-audit-v1.md、gate7-device-ab.md
P6.5 两轴传输 + 跨机 p65/ evidence-index.md、validation-status.md、code-review-findings.md
P3b / P4b Espryt 深化 p34b/ espryt-d1.md … espryt-d3.md
P7 Magma 全量迁移（含 Ph） p7/ PLAN-PH-P34B-P7.md、INTEGRATOR-DECISIONS-P7.md（ID-P7-1..63）、HANDOFF-2026-09-23.md、device-window-*/；审查稿在 handoff/
P12（已收官）server 自有屏幕窗口 p12/ PLAN-P12.md、INTEGRATOR-DECISIONS-P12.md、device/
P8 / P9 / P10 / P11 / P13（待排） p8/、p9/、p10/、p11/、p13/ 目前只有路线图上的完整范围与出口门

跨阶段：DEBTS.md（仍开放的债务与去向）、OPEN-QUESTIONS.md（开放问题全文，编号稳定）；handoff/（P7 的集成者审查稿，路径被 P7 交接文档引用，保持原位）；recovered/（从失败的 workflow 运行里捞回的 P0–P2 期材料，wf1 设计定稿前的计划草案、wf2 P0、wf3 P0.5、wf4 P1、wf5 P2；与阶段目录逐字节重复的副本已于 2026-09-24 删除，只留独有的）；perf-five-arm-20260928/（非阶段的五臂传输性能对比与瓶颈归因，2026-09-28）；anland/（非阶段的调研：MobileGL 给 Anland——root Android 上的 Wayland 宿主——当 GL 提供者，两边各要做什么，2026-09-30）。

旧引用怎么找

2026-09-24 整理时移动的文件（旧笔记、代码注释与契约里仍按旧名引用它们，文件名没变）：

旧位置 新位置
docs/Disaggregated/P5D-INPROC-PERFORMANCE.md p5d/P5D-INPROC-PERFORMANCE.md
docs/Disaggregated/P5E-RUNAHEAD.md p5e/P5E-RUNAHEAD.md
docs/Disaggregated/P5F-WIRE-COMPLETENESS.md p5f/P5F-WIRE-COMPLETENESS.md
docs/Disaggregated/P6-SPAWN-PLAN.md、P6-CONTRACT-DRAFT.md、P6-ENDSTATE-REVIEW.md p6/ 同名文件
docs/Disaggregated/CURRENT_STAGE_STATUS.md 并入 ../CURRENT_STAGE_PROGRESS.md；其中 P7 的出口门 / 已落地 / 真机三节在 p7/README.md，P12 部分在 p12/README.md
旧 CURRENT_STAGE_PROGRESS.md 的 P6.5 第一波与 P6 收官快照 p65/README.md、p6/README.md
当前阶段页的明细（带裁定编号的表、余项清单、证据位置） p12/README.md 的"当前状态详情"节
docs/Disaggregated/devices/pin-verification-2026-09-07.md ../guide/pin-verification-2026-09-07.md
ARCHITECTURE.md 的设计正文（§1–§17、附 A / B） ../design/ 下十个文件，编号不变；对照表在 ../ARCHITECTURE.md
旧 README.md 的构建运行、代码地图、术语；旧 ROADMAP.md 的通用纪律 ../guide/

按编号引用的旧章节（小节编号在新位置原样保留）：

旧引用 现在在
MEASUREMENTS.md §1 / §2 / §3 / §4 / §5 p0 / p1 / p2 / p3a / p4a 的"实测"节
MEASUREMENTS.md §6 / §7 / §8 / §9 p5 / p5b / p5c / p5d
MEASUREMENTS.md §10 / §11 / §12 / §13 p5e（§10、§11）/ p6 / p34b
ARCHITECTURE.md §17.1–§17.4 / §17.5 / §17.6 / §17.7 p5 / p5b / p5c / p5e 的"落地形状"节（../design/10-phase-shapes.md 留一张索引表）
ROADMAP.md 阶段表某行、"P5c 计划与审计"、"立即的下一项：P6.5 第一波"、债务表、开放问题 对应阶段 README.md 的"阶段表行"节；p5c；p65；DEBTS.md（历史全表在 p5b 末节）；OPEN-QUESTIONS.md
ARCHITECTURE.md:NNN、MEASUREMENTS.md:NNN 这类行号引用 指向写下它时的那个版本，今天已不对应；按上下文所说的节去找，或 git show <当时的头>:docs/Disaggregated/<文件>
~/w7/notes/<phase>/<file>.md docs/Disaggregated/notes/<phase>/<file>.md（这些笔记原先只存在于一台机器的 ~/w7/notes/）

收录规则
收录 全部 .md 笔记，以及阶段自己决定入库的小脚本、判读工装与证据摘要（如 p7/device-window-*/、p12/device/、p12/gate/）
不收录 大体积、随每次运行重新产生、只在产生它的机器上有意义的证据数据：完整运行日志、APK 与 .idsig、nm 转储、设备 logcat。上层文档引用它们时给的是路径，不是内容

新阶段开工时建 notes/<阶段>/，把计划、裁定与报告都放进去；阶段收官时补齐该目录的 README.md 汇总，顶层索引只改一行。

不受 citation lint 管

CI 的文档引用 lint 只检查顶层、design/ 与 guide/（.github/workflows/test.yml），本目录不在其中，这是有意的：笔记里的 file:line 写在各自当时的代码头上，拿今天的 HEAD 解析必然大面积失败——那是它们作为历史记录的正确状态。要核对某份笔记的引用，用它自己声明的那个 revision：

python3 scripts/check_doc_citations.py --rev <当时的头> docs/Disaggregated/notes/<phase>/<file>.md
Reference in New Issue View Git Blame Copy Permalink