| commit | a7ccbe2a5abb141d714d5d1e66bb4babbd642fef | [log] [tgz] |
|---|---|---|
| author | Ed Coyne <edcoyne@google.com> | Thu Oct 25 10:47:23 2018 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Oct 30 23:57:06 2018 +0000 |
| tree | 8618d8701ad5b1c23fea321d3b91e4c1bf3accb0 | |
| parent | 03ffcd1ab1668700c05cc49d6efae037d907eda7 [diff] |
[docs] Minor edits to scheduler doc. * Clarify "priority queue" in scheduler doc. Scheduler design uses the term "priority queue" in a way that isn't exactly consistent with the data structure known as a priority queue. We add a small clarifying statement to the reader so they can move past that confusion. * Change misleading terms about which priority queue will be used after a thread is preempted to be more ambiguous. Tested: viewed in gittles. Change-Id: I5e91aca8e47f5f3705689c7ba17603ce47ab9e0b
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.