generated from erix/meta
[FEATURE] Capture bounded firmware processor topology before handover #31
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/bootloader#31
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem and motivation
The kernel currently discovers processors by following raw ACPI addresses after firmware handover. Processor discovery needs immutable topology data, not continuing access to firmware tables.
Proposed behavior and scope
Capture enabled LAPIC and x2APIC processor IDs while the bootloader holds its original live UEFI/configuration-table context. Bound every table read using the original firmware memory types and lengths, then serialize a counted immutable topology snapshot through the BootKernel wire contract. Preserve full-width IDs, discovery order and single-processor systems. Coordinate the kernel consumer and remove its superseded raw discovery path.
Authority, security and reliability
Read provenance comes from the original UEFI entry context and valid firmware table storage. Normalized free/reserved memory labels, checksums and numeric addresses cannot grant read access. Validate every header and full span before following it; reject malformed lengths, checksum failures, duplicate enabled IDs, truncated records and allocation failures. Copy only topology data into ordinary retained handoff storage and release temporary allocations before firmware exit. The snapshot conveys neither firmware-read permission nor processor startup ownership.
Acceptance criteria
Alternatives and tradeoffs
Transferring firmware-read authority into the kernel would retain a larger boundary and require another authority-bearing interface. Capturing the needed IDs in the bootloader keeps that access within its existing firmware lifetime.
Tracking and rollout
Implemented in #32, building on #29 and the scoped paging correction #30. Coordinate lib-handoff#11 and kernel#140. Preserve known handoff compatibility; no permanent firmware alias or synthetic processor ID is introduced.
The bounded firmware reader and counted snapshot producer are implemented in #32. Processor IDs are copied before firmware exit, temporary owners are released before handover, and the kernel receives no firmware pointer. Coordinated native image acceptance remains on the checklist.