[PERF] Runtime Introspection Syscalls
This commit is contained in:
@@ -9,6 +9,8 @@ It complements [`16-host-abi-and-syscalls.md`](16-host-abi-and-syscalls.md), whi
|
||||
|
||||
Unless a domain chapter explicitly narrows behavior further, this chapter is the transversal policy for all syscalls in v1.
|
||||
|
||||
Per `DEC-0009`, guest-visible syscalls must not exist merely for debug convenience or certification plumbing. Those concerns belong to host-owned tooling.
|
||||
|
||||
## 1 Error Model: Faults vs Status Returns
|
||||
|
||||
Syscalls use a status-first hybrid model.
|
||||
@@ -61,6 +63,7 @@ Practical rule:
|
||||
|
||||
- `void` is allowed only for operations whose non-fault path is effectively unconditional success;
|
||||
- any operation with a meaningful operational non-success outcome must surface that outcome through `status`, not through absence of return values.
|
||||
- debug-only or certification-only convenience calls are not justified public ABI even if they could be given a valid return shape.
|
||||
|
||||
### No-op policy
|
||||
|
||||
@@ -77,6 +80,14 @@ This means operational problems must not be reclassified as:
|
||||
- `Trap`, when the failure is not structural;
|
||||
- `Panic`, when the failure is not an internal invariant break.
|
||||
|
||||
### Diagnostics boundary
|
||||
|
||||
These policy constraints also apply to observability surfaces:
|
||||
|
||||
- host-owned inspection and certification consumers may use runtime telemetry and internal host/runtime integration paths;
|
||||
- guest-visible syscalls must be justified by machine-facing operational needs, not by tooling convenience;
|
||||
- textual JSON diagnostics are not valid long-term public syscall ABI.
|
||||
|
||||
## 2 Capability System
|
||||
|
||||
Each syscall requires a declared capability.
|
||||
@@ -141,7 +152,7 @@ The system may account for:
|
||||
- cycles spent in syscalls;
|
||||
- allocations triggered by syscalls.
|
||||
|
||||
This keeps host interaction visible in certification, telemetry, and profiling.
|
||||
This keeps host interaction visible in host-owned certification, telemetry, and profiling.
|
||||
|
||||
## 6 Blocking and Long Operations
|
||||
|
||||
|
||||
Reference in New Issue
Block a user