plan capsule blocks: the offset is the RAM block count, a Kconfig symbol (Captain Bob)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
This commit is contained in:
Claude
2026-11-18 17:21:39 +00:00
parent 1061433791
commit 5210abaa4e
@@ -45,8 +45,13 @@ Written 2026-11-18, from the capsules talk with Captain Bob. It records the ruli
final."** A page written to a block number already in use overwrites it; what was there is gone.
Which write wins follows from the load order, which is fixed, so it is deterministic. A shared
number is not an error, so `mkcapsule`'s cross-capsule collision check (`:846-879`) goes.
3. **The knobs:** which ones set the offset (where the VM's RAM ends), for v3 and for v4. v4's node
has its own block window (`V4_BLOCK_SLOTS`).
3. ~~The knobs~~ **Ruled: the RAM block count.** The offset is the VM's user RAM block count,
`BLK_RAM_BLOCKS - BLK_FORTH_SYS_RESERVED` (2048 today, `v3/include/block_subsystem.h:78-88`).
- It becomes a Kconfig symbol.
- The kernel reads it.
- `mkcapsule` is given it at build time in place of its literal 2048 (`:414`, `:1094`).
v4's node window (`V4_BLOCK_SLOTS`) is not the source of the offset.
4. **Where the pages land before relocation:** in the kernel's block store at `n`, or straight into
the relocated slot.
5. **The range tables and `BLOCK_MAP.md`:** go, or become a record of what each capsule uses.