Core Servers

Implement init as the first userspace process. Why it matters: init (PID 1) anchors the entire userspace; every other service is spawned from it. Focus on `init_task` in `kernel/src/main.rs` while you trace the snippet.

/// init task: creates service endpoints, registers them, spawns servers.
fn init_task() -> ! {
    // Create IPC endpoint for the console service.
    let console_ep = ipc::endpoint::ENDPOINTS.lock().create();

    // Register in the service registry so clients can look it up by name.
    ipc::registry::register("console", console_ep)
        .expect("[init] failed to register console service");

    log::info!("[init] service registry: console={:?}", console_ep);

    // Spawn service tasks and a demo client.
    // kbd_server_task creates its own notification internally and does not
    // serve IPC clients in Phase 7 — no endpoint registration needed.
    task::spawn(console_server_task, "console");
    task::spawn(kbd_server_task, "kbd");
    task::spawn(console_client_task, "console-client");

    log::info!("[init] service set started — yielding");
    loop {
        task::yield_now();
    }
}

View on GitHub

Add a simple service registry for discovering early services. Why it matters: Clients need a well-known mechanism to find services by name without hardcoded endpoint IDs. Focus on `Registry` and `register` in `kernel/src/ipc/registry.rs` while you trace the snippet.

struct Registry {
    entries: [Option<Entry>; MAX_SERVICES],
    count: usize,
}

View on GitHub

Add a simple service registry for discovering early services. Why it matters: Clients need a well-known mechanism to find services by name without hardcoded endpoint IDs. Focus on `Registry` and `register` in `kernel-core/src/ipc/registry.rs` while you trace the snippet.

/// Dynamically growable service registry — name-to-endpoint mapping with
/// ownership tracking.
pub struct Registry {
    entries: Vec<Option<Entry>>,
    count: usize,
}

View on GitHub