commit | bdbcebf4d5b1492d2b51bdd6d51d572a52e34f2b | [log] [tgz] |
---|---|---|
author | Travis Geiselbrecht <travisg@google.com> | Thu Mar 15 19:11:52 2018 -0700 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Mar 16 20:45:23 2018 +0000 |
tree | 6e9444f52675f459989606d4aa3394da671bf418 | |
parent | e0357ff5ad4ce4224870968017086c1b6a1bd784 [diff] |
[scripts][build/run-zircon] fix run-zircon to pass the build type args through If using -b, run-zircon was constructing args as if to call build-zircon but was still calling make-parallel. Fix this and make sure build-zircon passes through extra args to the make invocation. Change-Id: I60d37a96af525edc8846f1a951d82e6f4be902e2
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.