|author||Scott Graham <firstname.lastname@example.org>||Mon Jan 14 16:55:08 2019 -0800|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Tue Jan 15 07:19:57 2019 +0000|
[libc] Remove use of random() from system/utest/evil/evil.c This test is just using this to decide how to run a spammy malloc test, so a simple cprng_draw() and mod is fine. ZX-3307 #comment [libc] Remove use of random() from system/utest/evil/evil.c Test: CQ Change-Id: I3a3e7b8d3f7fd93b4c8f0219b74a9d0f3bd81aa5
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.