| commit | e04dcfe00975d958f7d5dcf9ba940521a0e3c219 | [log] [tgz] |
|---|---|---|
| author | Nick Maniscalco <maniscalco@google.com> | Fri Jan 04 12:45:04 2019 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Jan 15 22:31:57 2019 +0000 |
| tree | 3c6b6f008ecd5eb3ed7210755fbc54327d4dfc5f | |
| parent | 3aed6f05039d7e226c4aca3d894221f626151407 [diff] |
[syscalls][job] Extend zx_job_set_policy to support timer slack No behavior change. zx_job_set_policy can now be used to set a job's timer slack. However, slack is not yet utilized by all eligible syscalls. That will happen in a future change. Bug: ZX-931 #comment Extend zx_job_set_policy Test: tests added to core-tests Change-Id: Ie80f82b4518287ce3baecec7b87cac3421ca547a
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.