commit | 48e3b1d0ea66062bb304c3d5de14f5f3213b6a9f | [log] [tgz] |
---|---|---|
author | Christopher Anderson <cja@google.com> | Mon Mar 19 11:54:20 2018 -0700 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Mar 20 00:30:30 2018 +0000 |
tree | f21136db0bfd8180cfd608ab62589afdae049e95 | |
parent | 83dd7df7e71bb844a94903ef362c410122c6f81a [diff] |
[runtests] Add garnet test defaults, don't exit on all failures This changes runtests to look at test directories for both zircon and garnet, and not consider it a fatal error if a given directory does not exist. It may be possible to better determine where to look for tests via directory traversal or stat checks, but it would increase the scope and complexity of this tool. Change-Id: I370a0db8c85a9f31e63c985e7edcbf8cbb9b38c1
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.