[FEATURE] Consume captured processor topology without firmware reads #140

Open
opened 2026-11-13 14:02:20 +01:00 by erikinkinen · 0 comments
Owner

Problem and motivation

Processor topology must survive the end of firmware access and installation of private Kernel roots. A physical table address cannot supply a lifetime or permission to read its backing.

Proposed behavior and scope

Consume the immutable counted snapshot in LibHandoff #10 and #11. Replace all Kernel firmware walks with one data decoder. CPU registration, startup resources and AP execution remain separate.

Authority, security and reliability

Bootloader captures data under its original bounded UEFI occupation. Kernel receives no firmware read role. Check complete extents, uniqueness and actual BSP membership before publishing topology. Reserve storage fallibly and preserve setup errors; never invent peers from a CPUID count.

Acceptance criteria

  • Decode known 2.1/2.2 inputs; distinguish absent and malformed snapshots and reject unsupported fields or extents.
  • Preserve sparse/full-width IDs, reject duplicates and missing BSP, and avoid a fixed CPU ceiling.
  • Remove raw RSDP/SDT traversal and arbitrary-lifetime physical slices; prevent Rootd launch after failed native SMP preparation.
  • Exercise the actual consumer with inert poisoned address metadata, malformed ranges and identity refusals.
  • Run a data-only diagnostic on coherent 1/2/4-vCPU images, without calling its results AP execution.
  • Update component documentation and the coordinated technical manual.

Alternatives and tradeoffs

Transferring firmware memory provenance would require another Kernel read role. Capturing only the needed data in Bootloader avoids that authority and reader. Larger address mappings retain the original lifetime problem.

Tracking and rollout

Build on Kernel #139, coordinate with Bootloader #31, and retain actual private-root/multicore acceptance in Kernel #123.

## Problem and motivation Processor topology must survive the end of firmware access and installation of private Kernel roots. A physical table address cannot supply a lifetime or permission to read its backing. ## Proposed behavior and scope Consume the immutable counted snapshot in [LibHandoff #10](https://git.erikinkinen.fi/erix/lib-handoff/issues/10) and [#11](https://git.erikinkinen.fi/erix/lib-handoff/pulls/11). Replace all Kernel firmware walks with one data decoder. CPU registration, startup resources and AP execution remain separate. ## Authority, security and reliability Bootloader captures data under its original bounded UEFI occupation. Kernel receives no firmware read role. Check complete extents, uniqueness and actual BSP membership before publishing topology. Reserve storage fallibly and preserve setup errors; never invent peers from a CPUID count. ## Acceptance criteria - [ ] Decode known 2.1/2.2 inputs; distinguish absent and malformed snapshots and reject unsupported fields or extents. - [ ] Preserve sparse/full-width IDs, reject duplicates and missing BSP, and avoid a fixed CPU ceiling. - [ ] Remove raw RSDP/SDT traversal and arbitrary-lifetime physical slices; prevent Rootd launch after failed native SMP preparation. - [ ] Exercise the actual consumer with inert poisoned address metadata, malformed ranges and identity refusals. - [ ] Run a data-only diagnostic on coherent 1/2/4-vCPU images, without calling its results AP execution. - [ ] Update component documentation and the coordinated technical manual. ## Alternatives and tradeoffs Transferring firmware memory provenance would require another Kernel read role. Capturing only the needed data in Bootloader avoids that authority and reader. Larger address mappings retain the original lifetime problem. ## Tracking and rollout Build on [Kernel #139](https://git.erikinkinen.fi/erix/kernel/pulls/139), coordinate with [Bootloader #31](https://git.erikinkinen.fi/erix/bootloader/issues/31), and retain actual private-root/multicore acceptance in [Kernel #123](https://git.erikinkinen.fi/erix/kernel/issues/123).
erikinkinen added this to the Alpha 1 milestone 2026-11-13 14:02:20 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/kernel#140
No description provided.