Microkernel
Subject: Computer and Technology noun /ˈmaɪ.kroʊˌkɜːr.nəl/ 1 definition
- operating-systems
- kernel-design
- system-architecture
- systems-programming
-
Definition (noun)
Entry #210 · UpdatedA Microkernel is an operating system kernel architecture that restricts privileged kernel-mode execution to only the minimal primitives needed to manage hardware—typically thread scheduling, basic address-space management, and inter-process communication. Higher-level operating system components, including device drivers, file systems, and network stacks, run in unprivileged user space as isolated server processes that communicate via message passing. By keeping the privileged trusted computing base small, this boundary isolates faults in individual services from the core kernel and strengthens modularity and security, trading extra context-switching and message-passing overhead for resilience compared to monolithic kernels.
Common Types
First-Generation Microkernels: Early architectures such as Mach that moved operating system subsystems into user-space servers while retaining relatively rich kernel abstractions, often incurring significant message-passing and context-switching overhead.
Second-Generation Microkernels: Strictly minimalist designs pioneered by the L4 family that reduce the kernel to a small footprint of threads, address spaces, and register-optimized synchronous communication to achieve near-monolithic performance.
Capability-Based Microkernels: Security-focused variants such as seL4 that govern all kernel resources through unforgeable capability tokens, enabling strict least-privilege isolation and formal mathematical verification of correctness.
Real-Time Microkernels: Deterministic systems such as QNX Neutrino tailored for safety-critical embedded environments, combining bounded-latency scheduling with user-space drivers that can be restarted independently after faults.
Example
In an automotive digital instrument cluster built on a microkernel such as QNX Neutrino, the Bluetooth and media drivers run as isolated user-space processes rather than inside privileged kernel mode. When a malformed frame triggers a segmentation fault in the Bluetooth driver, the kernel terminates only that process so a supervisor can restart it, leaving safety-critical CAN-bus telemetry and speedometer rendering uninterrupted.