generated from erix/meta
Preserve exact bootstrap page-table backing and permissions #30
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!30
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/exact-bootstrap-page-tables"
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
Make the bootstrap page-table planner count exactly the tables the mapper consumes. Preserve compatible original backing when rounded load pages share a page, split low identity mappings when read-only policy requires it, and reject conflicting translations or policies before changing tables.
Tracking and scope
Builds on #29. This fixes the paging component; dynamic-artifact production and whole-image kernel admission are separate work.
Architecture, authority and failure behavior
The existing UEFI allocation owns the exact table arena. Mapping requests describe geometry and policy; they do not grant backing memory. Keep the strict arena-consumption gate, reject physical rebinding and reserved control-window conflicts, and preserve neighboring permissions when splitting a huge leaf. The existing broad identity map and absence of NX policy are unchanged and are not claimed as solved here.
Validation evidence
Host tests execute the production planner and mapper using explicitly owned test storage. They do not prove firmware placement or guest execution.
Review checklist
WIP: Preserve exact bootstrap page-table backing and permissionsto Preserve exact bootstrap page-table backing and permissionsThe paging component is ready for review at
814d2841. Its original gates pass locally and current CI passes, including the actual UEFI build. The controls execute the production mapper and cover exact arena use, read-only splitting, compatible rounded-page sharing and refusal before mutation. Whole-image Kernel admission remains separate.