[FEATURE] Serve original cancellable public clock deadlines #4
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/timed#4
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 authorized deadlines and activity waits now exist, but Timed still serves only immediate clock snapshots and cooperatively polls its two legacy routes. Descriptor-readiness clients need original cancellable deadline delivery through their already delegated public clock service. They must not receive a direct native Time capability.
Proposed behavior and scope
Add a cap-free owned public request for an absolute monotonic nanosecond deadline, with an exact correlated completion. Retain multiple original pending deliveries in deployment-counted, compiler-described mapped storage. Preserve immediate monotonic/wall queries and private RTC input. Multiplex pending waiters through the earliest actual native timer, retire cancellation through the original native invocation, and explicitly watch both actual legacy receive bindings. Observe activity before inspecting every work source, and sleep only after no actionable work remains.
Integration must size and map the actual waiter arena from explicit deployment configuration before signing. No allocator, guessed waiter ceiling or new service grant is required. Long deadline requests use owned transport; legacy snapshot behavior remains compatible. Coordinate the request codec, actual service, packaging and later mediator consumer.
Authority, security and reliability
Only Timed's existing dedicated Time SEND binding may arm native deadlines. A public caller possesses only its actual delegated public service endpoint; a request ID, timestamp or copied owner selector grants no authority. Retain actual native delivery ownership before interpreting request evidence. Caller release and terminal cleanup must retire original waiting work and acknowledge that exact delivery. Binding loss, clock failure, storage exhaustion and malformed evidence must never fabricate elapsed time, leak an original timer or revive a replacement. Source errors remain errors. Preserve native result custody through definite capacity refusal and uncertain completion; failure to account for custody terminates the service instead of resuming ordinary admission.
Acceptance criteria
Checklist
Alternatives and tradeoffs
Direct Time grants to each mediator would widen authority. A single retained long request would block unrelated deadlines and snapshot queries. A fixed waiter array would impose a source-coded capacity. Deployment-counted mapped storage keeps the actual bound explicit. One earliest native timer avoids one hardware-facing owner per public waiter; cancellation scans remain bounded by admitted original storage and fair progress. Do not replace actual elapsed time with poll counts or cooperative yields.
Tracking and rollout
Depends on authorized native deadlines and the timer-routing repair. Implements the clock-service portion of descriptor readiness, tracked in phase completion. Coordinate Timed review, LibIPC review and Integration review. Full descriptor readiness remains open; both complete EriX guest generations and external Rust/LLVM guest rebuilding remain required and unperformed.
Counted public clock deadlines — 2 October 2026
One earliest native timer uses only Timed's existing Time SEND binding; no Time capability is delegated to clients.
Original caller cancellation, source failure, definite result-capacity refusal and uncertain timer/result custody remain distinct.
Image packaging requires explicit waiter capacity, validates pristine compiler geometry and checked native extent, expands the signed arena and shifts its terminal stack. Zero capacity deliberately refuses deferred admissions; padding never adds rows.
Its required TIMED_DEADLINES_OK marker follows all assertions. The dedicated scenario retains a 90-second external diagnostic budget; the existing time profile also requires the workload and actual APIC wake backend. Hosted adapters cannot fabricate guest success.
Original descriptor/provider subscriptions, mediator/client consumers, signal masks and complete poll/select workloads remain unfinished. Overall phase checklist acceptance is unchanged. Both complete EriX guest generations and rebuilding external Rust/LLVM inside EriX remain required and unperformed.
Related records and contracts
erikinkinen referenced this issue from erix/coreutils2026-10-02 13:23:12 +02:00
erikinkinen referenced this issue from erix/docs2026-10-02 13:23:14 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-10-02 13:23:22 +02:00
erikinkinen referenced this issue from erix/exsh2026-10-02 13:23:23 +02:00
erikinkinen referenced this issue from erix/extop2026-10-02 13:23:23 +02:00
erikinkinen referenced this issue from erix/fatd2026-10-02 13:23:24 +02:00
erikinkinen referenced this issue from erix/integration2026-10-02 13:23:27 +02:00
erikinkinen referenced this issue from erix/launchd2026-10-02 13:23:31 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-10-02 13:23:36 +02:00
erikinkinen referenced this issue from erix/lib-posixabi2026-10-02 13:23:37 +02:00
erikinkinen referenced this issue from erix/lib-stdio2026-10-02 13:23:38 +02:00
erikinkinen referenced this issue from erix/loaderd2026-10-02 13:23:40 +02:00
erikinkinen referenced this issue from erix/posixd2026-10-02 13:23:43 +02:00
erikinkinen referenced this issue from erix/procd2026-10-02 13:23:46 +02:00
erikinkinen referenced this issue from erix/ramfsd2026-10-02 13:23:46 +02:00
erikinkinen referenced this issue from erix/rootd2026-10-02 13:23:47 +02:00
erikinkinen referenced this issue from erix/ttyd2026-10-02 13:23:50 +02:00
erikinkinen referenced this issue from erix/vfsd2026-10-02 13:23:50 +02:00