commit | 4988ba5e04b98b669b88e3ba1ccb5e70bfb68b4a | [log] [tgz] |
---|---|---|
author | Scott Graham <scottmg@google.com> | Wed Dec 12 17:00:39 2018 -0800 |
committer | Scott Graham <scottmg@google.com> | Thu Dec 13 03:33:47 2018 +0000 |
tree | c6844a6351c5a040d8ab80684f7f1c15a1b6115f | |
parent | c639bf5a7bccacd33ddf533a63e4725319004241 [diff] |
[syscalls][docs] Fix a few DESCRIPTIONs that don't match SYNOPSIS https://fuchsia-review.googlesource.com/c/zircon/+/233524/ wishes that our documents were more structured than they really are in practice, so it's not currently landable. But manually looking through the warnings it emits points out a few mistakes, fixed here. ZX-2399 #comment [syscalls][docs] Fix a few DESCRIPTIONs that don't match SYNOPSIS ZX-3106 #comment [syscalls][docs] Fix a few DESCRIPTIONs that don't match SYNOPSIS Test: CQ Change-Id: I0ce85bec4d5d2e33adf1d06dee3a7ac883897c21
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.