commit | 73bd065d5857358e2722e5c248e3589c287d3f16 | [log] [tgz] |
---|---|---|
author | Nick Maniscalco <maniscalco@google.com> | Wed Sep 19 12:51:06 2018 -0700 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Sep 19 21:26:25 2018 +0000 |
tree | 1e7adeefeef94d533696f494df9087e067835dd2 | |
parent | 6c2ccb39b55f10094b7f7486baabbf81b664c4b5 [diff] |
[kernel][timer][test] Don't assert trylock result to eliminate test flake I was overzealous with my test assertions in Ie46d329d59cf00ed8d8d4e9c51b80fd4b7c6a517. While unlikely, the timer could certainly observe the cancel before the lock release so we can't assert on the result of trylock_or_cancel. Test: "k ut timer" in a loop on VIM2 for several mins, no failures Change-Id: I2f6c6e8a3fc39a024229676167cc55b84cf2df89
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.