[FEATURE] Define IPC progress and cancellation under contention for Alpha 1 #130

Open
opened 2026-11-12 22:27:55 +01:00 by erikinkinen · 0 comments
Owner

Problem and motivation

CPU fairness alone does not establish progress for competing IPC clients or control operations.

Proposed behavior and scope

Implement the Alpha 1 scope in kernel, lib-ipc and service owners. Follow the published Phase 6 requirements. Later-phase extensions remain separate.

Authority, security and reliability

Preserve explicit authority, original identity and resource custody across failure, cancellation and revocation. Apply security, reliability, then performance; names and observations must not create authority.

Acceptance criteria

  • Define progress and queue-selection policy under competing clients and long synchronous request chains.
  • Define cyclic-wait failure or an authorized cancellation/termination path that breaks the wait safely.
  • Demonstrate progress for eligible requests, cancellation and control operations under sustained contention.
  • Preserve committed effects, original identities and capability lifetimes during cancellation and cross-core races; priority donation remains Phase 7 work.

Alternatives and tradeoffs

Extend existing mechanisms where possible. Models and authored tests support the work but do not replace required original release-image evidence.

Tracking and rollout

Required by the Alpha 1 microkernel gate alongside the complete self-hosting gate. Link implementation PRs and dependencies here as they are established.

## Problem and motivation CPU fairness alone does not establish progress for competing IPC clients or control operations. ## Proposed behavior and scope Implement the Alpha 1 scope in kernel, lib-ipc and service owners. Follow the [published Phase 6 requirements](https://git.erikinkinen.fi/erix/docs/src/branch/main/phases/6.md). Later-phase extensions remain separate. ## Authority, security and reliability Preserve explicit authority, original identity and resource custody across failure, cancellation and revocation. Apply security, reliability, then performance; names and observations must not create authority. ## Acceptance criteria - [ ] Define progress and queue-selection policy under competing clients and long synchronous request chains. - [ ] Define cyclic-wait failure or an authorized cancellation/termination path that breaks the wait safely. - [ ] Demonstrate progress for eligible requests, cancellation and control operations under sustained contention. - [ ] Preserve committed effects, original identities and capability lifetimes during cancellation and cross-core races; priority donation remains Phase 7 work. ## Alternatives and tradeoffs Extend existing mechanisms where possible. Models and authored tests support the work but do not replace required original release-image evidence. ## Tracking and rollout Required by the [Alpha 1 microkernel gate](https://git.erikinkinen.fi/erix/integration/issues/207) alongside the [complete self-hosting gate](https://git.erikinkinen.fi/erix/integration/issues/65). Link implementation PRs and dependencies here as they are established.
erikinkinen added this to the Alpha 1 milestone 2026-11-12 22:27:55 +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/kernel#130
No description provided.