Fuchsia Internals, Vol. III: The Zircon Kernel
Volume III of the Fuchsia Internals series examines Zircon, the microkernel at the foundation of Fuchsia. At 43 pages, this report is the longest in the series. Subsequent subsystems like graphics, drivers, storage, and networking run in user space and rely on the primitives defined in this volume. For readers following Cocoapuffs on a RISC-V soft core, this volume documents the kernel behaviors encountered during that port. A link to the full document appears below.
Note on these reports: These reports were compiled automatically. Verify specific implementation details against upstream source code before relying on them.
Zircon replaces traditional Unix system calls with a compact set of kernel objects. User-space programs manipulate these objects through unforgeable handles that grant fine-grained rights. The kernel leaves almost all system policy to user-space components. Zircon manages only essential responsibilities: memory, thread scheduling, inter-process communication, and hardware access mediation.
What is inside
The report provides a five-part architectural tour:
- Part I: Foundations. The object, handle, and capability security model. This section covers the system-call ABI and the vDSO, the read-only memory page through which all system calls transition into the kernel.
- Part II: Tasks & scheduling. The job, process, and thread hierarchy. This part explains fair and deadline scheduling alongside core synchronization primitives.
- Part III: Memory. VMOs and VMARs, physical memory allocation, demand paging, and per-CPU kernel memory structures.
- Part IV: IPC, signals, interrupts, and time. IPC primitives including channels, sockets, FIFOs, signals, and ports.
- Part V: Platform. Hardware access objects such as MMIO regions,
interrupts, BTI instances, and IOMMU structures.
This section also details system boot, user-space bootstrap via
userboot, restricted mode, and multi-architecture support.
Syscall listings and a technical glossary make the report useful as an ongoing reference manual.
Architectural relevance for hardware engineers
Understanding Zircon’s kernel objects simplifies the remaining volumes in this series. The primitives translate directly into hardware concepts:
- A VMO serves as a managed DMA buffer.
- A handle functions like an authenticated bus transaction token.
- A channel operates as a bidirectional, typed streaming interface.
- A port aggregates asynchronous events like a prioritized interrupt controller.
- The BTI and IOMMU enforce hardware memory boundaries like an SMMU.
Mastering these core primitives clarifies the architecture of the remaining thirteen volumes.
Get the report
This is the third volume of a fourteen-part series; see the series announcement for the complete roadmap. Feedback and corrections are welcome.