| commit | 4c75a4a2e309a69e3f8adae44e14c6ba6094b412 | [log] [tgz] |
|---|---|---|
| author | Adam Barth <abarth@google.com> | Fri Sep 21 16:34:22 2018 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Sat Sep 22 05:29:22 2018 +0000 |
| tree | 9480490d959b201f2009b9213cdbb733d9e52b91 | |
| parent | 4e9adc419ee72c055ee2822d382feaf2b0c461f2 [diff] |
[fdio] Simplify process args and protocol names Now that we can recover the type of a socket from the kernel, we only need one process arg id for passing pipes, stream, and datagram sockets. Also, replace the duplicated FDIO_PROTOCOL_* definitions with their FIDL equivalent. Test: No behavior change Change-Id: I8b4bd830b9ef836827be6060cd0c4e0c096a7bbc
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.