commit | f3bfcb603e6e481658aced768f5b1e3dbbd550f0 | [log] [tgz] |
---|---|---|
author | George Kulakowski <kulakowski@google.com> | Mon Jan 28 13:53:35 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jan 30 01:22:11 2019 +0000 |
tree | c5e1108ed3a72b34cc2acd2c3f9ccdfccc3e8e6f | |
parent | 14207b63d4d41cedd9ac3f5958178721067d0ada [diff] |
[threads][test] Avoid scheduling flake in pthreads core test This test needs both to not hang indefinitely, and to return quickly on the typical expected success. As a comprimise, poll at high (relatively to scheduler and human perception of CQ, at least) frequency for 10 seconds, rather than once for much longer. This all correctly makes an int atomic, as it is accessed without other synchronization from multiple threads. Bug: FLK-35 #done Test: core tests Change-Id: I466106aae2364ae50ac3daba707d14a306d66925
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
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.