Architecture

Overview

Exokernel Design

AlJefra OS uses an exokernel architecture that minimizes the kernel's responsibility by delegating hardware management to user-level drivers and applications. The kernel provides minimal abstractions, giving applications direct (safe) access to hardware resources while maintaining isolation and security.

This design philosophy enables:

• Faster driver development and iteration
• Better resource utilization across different hardware platforms
• Easier customization for embedded and specialized systems
• Direct hardware access without microkernel overhead

Hardware Abstraction Layer (HAL)

The HAL provides a unified interface that abstracts away architecture-specific details. All drivers and kernel components use the HAL to interact with hardware, allowing the same portable C code to run on any supported architecture.

By implementing the HAL interface for each architecture, we achieve true code reuse: 22+ portable C drivers work identically on x86-64, ARM64, and RISC-V without modification.

Multi-Architecture Approach

Rather than maintaining separate OS versions for different architectures, AlJefra OS provides a single unified codebase with architecture-specific implementations of the HAL layer. This approach ensures:

• Consistent behavior across all platforms
• Simplified maintenance and bug fixes
• Faster integration of new features and drivers
• Reduced development time for new architectures

System Layer Diagram

┌─────────────────────────────────────────┐
│       Applications / AI Agent           │
├─────────────────────────────────────────┤
│      Kernel Core (C, portable)          │
│ scheduler · syscalls · driver loader    │
├─────────────────────────────────────────┤
│  Portable Drivers (C)                   │
│  NVMe·AHCI·VirtIO·e1000·WiFi·USB·PCIe  │
├─────────────────────────────────────────┤
│    HAL — Hardware Abstraction Layer     │
├────────────┬────────────┬───────────────┤
│  x86-64    │  AArch64   │   RISC-V 64   │
│ APIC/HPET  │ GIC/Timer  │ PLIC/mtime    │
└────────────┴────────────┴───────────────┘

HAL Interface

The Hardware Abstraction Layer defines a portable interface that all architectures must implement. Key HAL functions include:

Boot Sequence

AlJefra OS boots through the following sequence:

Power On
  ↓
Firmware (UEFI/BIOS)
  ↓
Bootloader (loads AlJefra kernel)
  ↓
HAL Initialization
  ├─ CPU: set up control registers, detect features
  ├─ MMU: enable virtual memory, set up page tables
  ├─ Interrupts: initialize interrupt controller
  └─ Timer: set up system timer
  ↓
Kernel Main
  ├─ Initialize kernel data structures
  ├─ Launch process manager and scheduler
  └─ Load bootloader drivers
  ↓
Bus Enumeration
  ├─ Scan PCIe/USB/Device Tree
  ├─ Discover available devices
  └─ Sync machine state and load device drivers via marketplace
  ↓
Network Initialization
  ├─ Initialize NIC driver
  ├─ Configure TCP/IP stack
  └─ Join network
  ↓
AI Bootstrap
  ├─ Register machine + desired apps with AlJefra Store
  ├─ Send hardware manifest to AlJefra Store
  ├─ Receive driver recommendations and queued work
  ├─ Download optimized drivers
  ├─ Verify signatures (Ed25519)
  └─ Install drivers
  ↓
System Ready
  └─ Applications can launch

Supported Architectures

Portable Drivers

All drivers are written in portable C and use the HAL interface. This ensures the same driver code runs identically on x86-64, ARM64, and RISC-V.