[Feat, Docs] (PipeStats, MEASUREMENTS): wire persistent-map-push to the bytes the client ships, rewrite the inventory line that called it unwired, and correct the persistent-map census from 20 to 21

This commit is contained in:
2026-09-11 14:31:46 -04:00
parent 142bf921d4
commit d9ade1e7cd
2 changed files with 17 additions and 4 deletions
+16 -3
View File
@@ -65,9 +65,22 @@
// payload, not resource bytes.
// NOT covered: Magma builds no such array (it issues one vkCmdDraw*
// per sub-draw), so this class is Espryt-only by construction.
// persistent-map-push Not wired in P0: today a persistent map is a permanent address
// space donation (D4/D-B4) that survives the whole monolith track,
// so there is no push to count until the IPC track breaks it.
// persistent-map-push WIRED IN P5 (b1), and only a split build can ever move it. The one
// site is BufferObject::PushMappedSpanBlock, i.e. the client shipping
// one MOBILEGL_IPC_PERSISTENT_BLOCK_KB block of a persistently mapped
// span because MGPipeApplyMapPersistent declined the adoption (R-6,
// tier T2). Zero in every monolith build, and that zero is CORRECT
// rather than missing: a persistent map there is a permanent address
// space donation (D4/D-B4), the application writes straight into GPU
// memory, and there is no push to count. A split run where this stays
// 0 has NOT reached T2.
// Read it against map-persistent-roundtrips (mpr), which it is
// ANTI-CORRELATED with: mpr counts acquisition ATTEMPTS - one per
// storage definition, the same number in both modes - and this counts
// the bytes the client had to ship because the attempt was declined.
// NOT double-counted with stage-buffer: that class is what a BACKEND
// stages out of a shadow it owns, and it explicitly excludes bytes an
// app writes through a persistent map (see its entry above).
// residual-value-block Placeholder, always 0 until P2 (plan section 6.3).
//
// Call classes