generated from erix/meta
Capture bounded firmware processor topology before handover #32
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/bootloader!32
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/firmware-topology-snapshot"
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?
Summary and rationale
Capture enabled processor IDs before firmware exit and pass a counted immutable snapshot to the kernel. Replace the later raw ACPI-pointer handoff with scoped reads through the original live UEFI configuration-table source.
Tracking and scope
Implements #31 atop #30; selects lib-handoff#11 and coordinates kernel#140.
Architecture, authority and failure behavior
Check original firmware storage types, complete spans, descriptor geometry, checksums and record boundaries before following tables. Preserve full-width IDs, discovery order and the existing startup record; reject duplicates and incomplete records. The snapshot is data and grants no firmware access or processor ownership.
Temporary ID and sorting storage has explicit owners. Copy IDs into the retained handoff, preserve them on console rebuilds, mark scratch storage future usable and release it before firmware exit. Zero the legacy RSDP field and remove the separate ACPI identity mappings. The existing broad low identity map remains separate work.
Validation evidence
Hosted readers and allocation controls do not establish actual firmware placement or AP startup.
Review checklist
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: Capture bounded firmware processor topology before handoverto Capture bounded firmware processor topology before handover