| commit | 5728a7f367007cf4573c798d57dc887b6ed5c2cd | [log] [tgz] |
|---|---|---|
| author | George Kulakowski <kulakowski@google.com> | Mon Sep 25 23:30:24 2017 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Sep 26 06:53:00 2017 +0000 |
| tree | c1aeced886f3bca9423a28b311fcaa3c7ee5cbb2 | |
| parent | 8e562ab97560a7ab10225091ba13640a48df2eee [diff] |
[dash] Fix error reporting from process_launch Before this, an int in the style of unix process exit() values (0 success, low numbers or high 120s different kind of bad, etc.) was returned, but logged as though it were a zx_status_t. This tweaks process_launch to return both styles and to print the more informative zx_status_t to stderr, with $? still set correctly to the unix style. Change-Id: I66cb615b2b83318829029f506f1e0f8156051eb4
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.