commit | f88d16ea6d7ad009796ce4460f705fa54cd5ebd2 | [log] [tgz] |
---|---|---|
author | Sean Klein <smklein@google.com> | Fri Jan 18 20:06:25 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Sat Jan 26 02:48:26 2019 +0000 |
tree | 58b60c2af050cf540a4f9b74dd9deeb5cfbe8f81 | |
parent | fd5d40ff42cccc23b8f8eb8fe6c012a3e1c02033 [diff] |
[third_party][zstd] Add rules.mk file, enabling compilation Test: Manually included as third_party/ulib/zstd, compiles. Change-Id: I96ede69e0431a3a2ee5c7f16ceaab8a29f9f4a89
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.