9c94a16d5a
A frozen guest still changes ~30000 words a second (180952-235973 in 6 s, 0.2% of the data) against 1863296 in 4 s (2.08%) while running. By region the frozen activity concentrates in 0xbf900000/0xbfa00000, in 0xbe0-0xbe3 00000, and in the 0x704/0x705 pages that the boot log shows are guest thread STACKS - frame churn, which is what a spinning thread looks like. Stated plainly as not-yet-interpretable: there is no matched region breakdown for the RUNNING case, because the control predates the summary. Those regions may simply be the busiest ones at all times, and one run fixes that. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PMRJjbxLqZtsb5Vb7KunPE