commit | 952d37c0580d2c7fd88dd21cf87b58d46ddc5e60 | [log] [tgz] |
---|---|---|
author | George Kulakowski <kulakowski@google.com> | Tue Jan 29 17:48:52 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Jan 31 10:45:25 2019 +0000 |
tree | c9ddeb4d8a64c166e5546884bc516c21da6b7892 | |
parent | c4204618d9538093b9d5f24d69f80d1a665a609d [diff] |
[fbl] Only allow fbl::atomic in the kernel Userspace should now always be using <atomic>. The kernel will migrate to a ktl-exposed subset shortly. Bug: ZX-3357 #comment Test: no functional change Change-Id: Idc986ef47a996d2080d15ab680dc0b2255bb5c8d
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
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.