[FEATURE] Retain private address spaces through native process switching #123
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#123
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
Native process execution needs hardware-isolated address spaces with explicit ownership through scheduling, faults and teardown. This is required for independent POSIX processes and the Alpha 1 microkernel demonstration.
Proposed behavior and scope
Retain private page-table roots and their real backing from creation through native entry and return. Each CPU must own its actual active, outgoing and transitioning roots. Preserve the Kernel, entry-stack and controller mappings required during a switch.
Coordinate this Kernel backend with target-memory construction and fault continuations. Existing source ownership remains required; a CR3 value or root identifier cannot construct an address-space owner.
Authority, security and reliability
Keep user mappings private and non-global. Borrow tables only through retained root resources and the original execution/selection source. Finish old-root user-packet borrows before switching. Preserve old and new root, frame and controller duties through failed preflight or partial transition.
Reclaim backing only after actual CPU departures and required TLB invalidations. Retain optional boot mappings only for their real users, and preserve valid module retirement. Source withdrawal, logical task state and reference counts alone do not prove hardware retirement.
Acceptance criteria
Alternatives and tradeoffs
A shared root or an idle-state check does not establish private address-space ownership. Reuse the owned supervisor hierarchy and retained backing where their source and lifetime contracts suffice. Resolve root-slot reentrancy and optional Kernel-mapping lifetimes before accepting physical activation.
Tracking and rollout
Depends on the ownership work in #121 and coordinates with #122. Part of Alpha 1 completion. Enable native paths after the complete producer/consumer contract and physical acceptance agree.
erikinkinen referenced this issue from erix/bootloader2026-11-13 13:59:04 +01:00