Consume captured processor topology without firmware reads #142
No reviewers
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!142
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/retained-processor-topology-intake"
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?
Read processor identities from Bootloader's immutable counted snapshot instead of following RSDP/SDT addresses in Kernel. Check uniqueness and actual BSP membership before publishing topology; a CPUID count cannot invent peer identities. Native setup errors prevent Rootd launch.
Builds on #139, LibHandoff #11 and Bootloader #32. Design: #140; manual: Docs #99. The snapshot grants no processor or firmware-read authority.
The captured-topology data cases now pass in QEMU/OVMF with 1, 2 and 4 vCPUs, reporting IDs
[0],[0, 1]and[0, 1, 2, 3]. The real dynamic image uses Kernel #141 (2283a382), Bootloader #36 (0776f2cc) and Integration #783. The topology producer and consumer module are byte-identical to this PR; the companion fixes the separately tracked runtime-symbol lookup in Bootloader #35. Each guest reaches Kernel entry, owned-stack preparation andPROCESSOR_TOPOLOGY:DATA_OK, then exits through the expected success path. This completes the topology data requirement and does not establish AP execution or private-root confinement.WIP: Consume captured processor topology without firmware readsto Consume captured processor topology without firmware reads