generated from erix/meta
[FEATURE] Hand over original x86 processor startup allocations #28
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#28
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 needs the original paging arena, BSP stack and low-memory scratch allocations before it can start application processors reliably.
Proposed behavior and scope
Allocate separate retained trampoline and real-mode stack pages through the live UEFI services. Emit their actual extents, the original PML4/table arena and the original BSP stack in the BootKernel v2.1 startup record. Build on #26 and the startup-resource wire contract.
Authority, security and reliability
UEFI allocation ownership supplies the physical storage. The record describes that original ownership; it grants no authority by itself. Reserve every retained allocation as bootloader-owned memory through handover. Release partial allocations on failure, and retain storage after successful firmware exit. Derive all addresses from actual allocations.
Acceptance criteria
Alternatives and tradeoffs
Fixed scratch addresses and sampled CR3 values cannot establish original allocation ownership. Explicit retained resources require coordinated producer and consumer updates.
Tracking and rollout
Depends on #26 and lib-handoff#8. Select lib-bootimg#4 for its compliant transitive main-branch source identities. Coordinate native activation and acceptance with kernel#11. Keep the new producer separate from artifact publication policy.
The original-allocation producer is implemented in #29, including scoped low-memory/BSP stack owners, retained memory-map reservations and BootKernel v2.1 serialization. Coordinated native allocation-failure and 1-, 2- and 4-CPU acceptance remain open with the kernel consumer. The matching manual contract is in docs#98.