commit | b716e5c224dab44b573d7ce1bafce89a61e956ab | [log] [tgz] |
---|---|---|
author | Scott Graham <scottmg@google.com> | Thu Dec 13 14:58:47 2018 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Dec 14 00:57:35 2018 +0000 |
tree | 9e14dbbaf2dd5ff9b6d171270e9671b2275f58eb | |
parent | e2a7ebafffec2840995491510ef511de8b7187ea [diff] |
[syscalls][docs] Cross-link syscall documentation This uses the format [`zx_syscall()`] inline, and defines a reference at the bottom of the file, to avoid having to stutter the syscall name both as inline text and as the .md file in () after the []. The references at the bottom of the file are not included in rendered output. (Thanks bruce.mitchener for the suggested format.) Additionally, replace existing spellings of syscalls that vary in style, sometimes prefixing with zx_, sometimes including () inside bold, sometimes both, and sometimes neither. On a syscall's own page, it is not linked, and is instead simply `zx_syscall()`. There are some existing references to syscalls (primarily those that were already linked) that are not updated by this. Maybe later, or manually. See the gitiles link for channel_call.md for an example result. ZX-3106 #comment [syscalls][docs] Cross-link syscall documentation Test: CQ Change-Id: Icac7c50251012af3580c130553d1bfd640fb3eff
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.