[FEATURE] MK9: Demonstrate functional SMP on two and four CPUs #206

Open
opened 2026-10-30 09:30:46 +01:00 by erikinkinen · 0 comments
Owner

Problem and motivation

Alpha 1 needs direct evidence that EriX functions as a secure microkernel OS. Demonstrate concurrent userspace execution, cross-core IPC, scheduling, memory isolation and safe revocation on 2–4 CPUs.

Proposed behavior and scope

Demonstrate this requirement on the actual x86-64 QEMU/OVMF release image, using the applicable 1, 2 and 4-vCPU configurations. This strengthens architectural acceptance without adding production-scale features.

Authority, security and reliability

Cross-core scheduling, mappings, capability use/revocation and reclamation must preserve the same security guarantees as the single-core baseline. Apply security, reliability, then performance.

Acceptance criteria

  • Run concurrent userspace workloads and cross-core IPC on both 2 and 4 vCPUs, with a 1-vCPU baseline.
  • Verify remote TLB invalidation, exclusive thread execution, concurrent capability operations and safe resource reclamation.
  • Repeat negative tests, fault injection and concurrency stress on the actual release image.
  • Publish source-linked release-image results and document relevant kernel/userspace responsibilities and privileged-service boundaries.

Scheduling and progress dependencies

Alternatives and tradeoffs

Isolated unit tests support this gate but do not establish end-to-end acceptance. Production SMP scaling, NUMA, CPU hotplug, networking, a graphical desktop, broad hardware support, comprehensive service supervision, full POSIX compliance and formal verification remain beyond Alpha 1.

Tracking and rollout

Part of the Alpha 1 microkernel demonstration gate, alongside the existing self-hosting acceptance. Keep implementation dependencies and evidence linked here.

## Problem and motivation Alpha 1 needs direct evidence that EriX functions as a secure microkernel OS. Demonstrate concurrent userspace execution, cross-core IPC, scheduling, memory isolation and safe revocation on 2–4 CPUs. ## Proposed behavior and scope Demonstrate this requirement on the actual x86-64 QEMU/OVMF release image, using the applicable 1, 2 and 4-vCPU configurations. This strengthens architectural acceptance without adding production-scale features. ## Authority, security and reliability Cross-core scheduling, mappings, capability use/revocation and reclamation must preserve the same security guarantees as the single-core baseline. Apply security, reliability, then performance. ## Acceptance criteria - [ ] Run concurrent userspace workloads and cross-core IPC on both 2 and 4 vCPUs, with a 1-vCPU baseline. - [ ] Verify remote TLB invalidation, exclusive thread execution, concurrent capability operations and safe resource reclamation. - [ ] Repeat negative tests, fault injection and concurrency stress on the actual release image. - [ ] Publish source-linked release-image results and document relevant kernel/userspace responsibilities and privileged-service boundaries. ### Scheduling and progress dependencies - [ ] [Support full configurable preemption for Alpha 1](https://git.erikinkinen.fi/erix/kernel/issues/129) - [ ] [Define IPC progress and cancellation under contention for Alpha 1](https://git.erikinkinen.fi/erix/kernel/issues/130) ## Alternatives and tradeoffs Isolated unit tests support this gate but do not establish end-to-end acceptance. Production SMP scaling, NUMA, CPU hotplug, networking, a graphical desktop, broad hardware support, comprehensive service supervision, full POSIX compliance and formal verification remain beyond Alpha 1. ## Tracking and rollout Part of the [Alpha 1 microkernel demonstration gate](https://git.erikinkinen.fi/erix/integration/issues/207), alongside the [existing self-hosting acceptance](https://git.erikinkinen.fi/erix/integration/issues/65). Keep implementation dependencies and evidence linked here.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:23 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/integration#206
No description provided.