[FEATURE] Consume captured processor topology without firmware reads #140
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/kernel#140
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
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
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.