Daniel Samson
452080e997
Time is a kernel concern in danos: the kernel owns the scheduling timer and already exposes monotonic time via the clock/sleep/timer_bind syscalls, so a userspace time service would be a redundant, slower path. This adds the generic runtime.time module over those syscalls, retires the two demonstration drivers, reorganizes the milestone docs, and makes the monotonic clock correct on Intel, AMD, and inside any VM. runtime.time (library/runtime/time.zig) - Instant/Duration interface: now, sleep, spin, after, monotonicNanos, available - a thin layer over system.clock/sleep/timerOnce; unit-tested arithmetic Remove the demo drivers hpet and bus (a teaching example belongs in the docs, not shipped in the tree) - system/drivers/ now holds only real drivers: pci-bus, ps2-bus, usb-xhci-bus - device-manager end-to-end test repointed to pci-bus (asserts on kernel state: the process table and the device tree, not a racy serial marker) - device_register containment moved to a new in-kernel `containment` test - the driver-model worked example moved inline into docs/drivers.md Reorganize milestone docs into topic docs - m17-m18 / m19-m20 / m21 plans dissolved into process-lifecycle, device-manager, discovery, and acpi docs; new docs/power.md and docs/timers.md; ~20 citations repointed; plan docs deleted TSC reliability (apic.zig, smp.zig, cpu.zig, kernel.zig) - check the invariant-TSC bit (CPUID 0x80000007 EDX[8]) on Intel and AMD - cross-core "warp" check at SMP bring-up, pairwise BSP<->AP as each core comes up - fall back to the HPET clocksource when the TSC is not invariant (a bare VM) or not synchronized (a warp), switched continuously so time never jumps - boot log reports the outcome; new tsc-sync test exercises the TSC + warp path Verified: zig build; zig build test; 60/60 QEMU cases (incl. new containment and tsc-sync).
69 lines
2.4 KiB
Zig
69 lines
2.4 KiB
Zig
//! The power protocol (docs/power.md): system power's domain-named surface,
|
|
//! registered under `ServiceId.power`. On x86 the acpi service serves it; on
|
|
//! ARM a PSCI/mailbox service will register the same id — subscribers never
|
|
//! learn which firmware they are on (docs/discovery.md — firmware neutrality).
|
|
//! The vfs-protocol pattern: extern-struct messages, a version, reserved fields.
|
|
|
|
/// The protocol version a client states nowhere yet — reserved for the day a
|
|
/// handshake needs it; requests carry it so a mismatch can be refused loudly.
|
|
pub const version: u16 = 1;
|
|
|
|
pub const Operation = enum(u8) {
|
|
/// Subscribe to power events: the subscriber's endpoint rides as the
|
|
/// call's capability (the input/device-manager pattern); events arrive on
|
|
/// it as buffered messages carrying an `EventMessage`.
|
|
subscribe = 1,
|
|
/// Orderly shutdown's last step: enter S5. Accepted only from PID 1
|
|
/// (init) — the process that has already run the stop sequence over
|
|
/// everything else.
|
|
shutdown = 2,
|
|
/// The published event payload (never sent *to* the service).
|
|
event = 3,
|
|
};
|
|
|
|
/// What happened. The vocabulary is hardware-neutral: a lid is a lid whether
|
|
/// ACPI or a PSCI mailbox reported it.
|
|
pub const Event = enum(u8) {
|
|
power_button = 1,
|
|
lid = 2,
|
|
ac = 3,
|
|
battery = 4,
|
|
/// A device notification that maps to none of the named events — the
|
|
/// `code` and `hid` fields say which device and what code.
|
|
notify = 5,
|
|
};
|
|
|
|
pub const Subscribe = extern struct {
|
|
operation: u8 = @intFromEnum(Operation.subscribe),
|
|
reserved0: u8 = 0,
|
|
version: u16 = version,
|
|
reserved1: u32 = 0,
|
|
};
|
|
|
|
pub const Shutdown = extern struct {
|
|
operation: u8 = @intFromEnum(Operation.shutdown),
|
|
reserved0: u8 = 0,
|
|
version: u16 = version,
|
|
reserved1: u32 = 0,
|
|
};
|
|
|
|
/// A published event, as the buffered-message payload subscribers receive.
|
|
pub const EventMessage = extern struct {
|
|
operation: u8 = @intFromEnum(Operation.event),
|
|
/// An Event value.
|
|
event: u8,
|
|
reserved0: u16 = 0,
|
|
/// The device notification code (Notify's second argument), or 0.
|
|
code: u32 = 0,
|
|
/// The notifying device's hardware id (EISA-decoded), or all zero.
|
|
hid: [8]u8 = .{0} ** 8,
|
|
};
|
|
|
|
pub const Reply = extern struct {
|
|
status: i32,
|
|
reserved: u32 = 0,
|
|
};
|
|
|
|
/// Upper bound on any message in this protocol — sizes endpoint buffers.
|
|
pub const message_maximum = 64;
|