generated from erix/meta
[FEATURE] Hand over original x86 processor startup resources #8
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/lib-handoff#8
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
AP startup and safe private-root bootstrap need the original loader-owned table,
stack and low-memory resources to remain accounted for through handover. A memory
map or matching physical address describes a resource; it does not transfer it.
Proposed behavior and scope
Extend the bootloader-to-Kernel handoff to BootKernel version 2.1 with an optional x86 startup
resource record. Retain the 200-byte base header and add a flagged 16-byte extension
containing the record offset, size and reserved-zero field. The record describes
the original PML4/table arena, BSP stack and any actual AP trampoline/real-mode
stack allocations. Keep physical allocation and transfer in the bootloader and
Kernel; this library supplies structural parsing and consistency checks only.
Authority, security and reliability
The bootloader must own and retain the actual allocations across ExitBootServices.
Only the original initial Kernel handover may turn that real grant into native
borrow/occupation roles. Decoded records cannot construct authority at runtime.
Check complete reserved-memory coverage, alignment, arithmetic and disjointness.
Retain all startup resources through uncertain dispatch; a timeout is not evidence
that a CPU stopped referencing them. Do not restrict final Kernel roots to low
memory or substitute an observed CR3 for an original startup-root loan.
Acceptance criteria
exact version, flags, reserved fields and metadata overlap checks.
distinguish absent AP scratch from an actual grant.
usable low entry resource and separate actual real-mode stack.
INIT/SIPI, preserve all owners through failure and prevent uncertain scratch reuse.
cases; preserve existing boot and native execution workloads.
lifetime rules, keeping physical native acceptance separate from wire tests.
Alternatives and tradeoffs
A low-address restriction on the whole Kernel would constrain ordinary memory
allocation without providing ownership. Retaining an actual low startup root and
then installing the prepared final root keeps the architectural entry constraint
local to startup. The record remains descriptive so the wire crate does not gain
hardware operations or resource-import APIs.
Tracking and rollout
Wire implementation: #9.
Coordinate lib-handoff, Bootloader and Kernel changes with
Kernel native execution and
Phase 6 completion.
Keep Cargo dependencies on main and select the coherent development sources in CI.