| commit | 1e354201879c0d3f89eb165bf9fdce499d678769 | [log] [tgz] |
|---|---|---|
| author | Mark Seaborn <mseaborn@google.com> | Thu Jan 25 19:46:19 2018 +0000 |
| committer | Mark Seaborn <mseaborn@google.com> | Thu Jan 25 20:29:49 2018 +0000 |
| tree | 46bea2c3e5128ce72d6bdf4e4344a7b526010a3c | |
| parent | e646a7bf88ed4febe25ea3d8678ccc1f81c825ac [diff] |
[kernel] Revert "[kernel][interrupts] Add assertion to every interrupt-handling function" This reverts commit cae96aef07ff38db6e1ad7f05444758531c3e764. That change caused a kernel assertion failure via the following path: sys_mmap_device_io() -> IoBitmap::SetIoBitmap() -> mp_sync_exec() -> mp_mbx_generic_irq() ZX-1490 Change-Id: Ic2362d000be7b4e021c6942cc6d0f9550dd15649
Zircon is the core platform that powers the Fuchsia OS. Zircon is composed of a microkernel (source in kernel/...) as well as a small set of userspace services, drivers, and libraries (source in system/...) necessary for the system to boot, talk to hardware, load userspace processes and run them, etc. Fuchsia builds a much larger OS on top of this foundation.
The canonical Zircon Git repository is located at: https://fuchsia.googlesource.com/zircon
A read-only mirror of the code is present at: https://github.com/fuchsia-mirror/zircon
The Zircon Kernel provides syscalls to manage processes, threads, virtual memory, inter-process communication, waiting on object state changes, and locking (via futexes).
Currently there are some temporary syscalls that have been used for early bringup work, which will be going away in the future as the long term syscall API/ABI surface is finalized. The expectation is that there will be about 100 syscalls.
Zircon syscalls are generally non-blocking. The wait_one, wait_many port_wait and thread sleep being the notable exceptions.
This page is a non-comprehensive index of the zircon documentation.