| commit | 9c6885ade29d48e09effe09775cf6600cf7a71fd | [log] [tgz] |
|---|---|---|
| author | Adam Barth <abarth@chromium.org> | Sun Jun 03 23:13:50 2018 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Jun 04 19:56:43 2018 +0000 |
| tree | ac5af1cafa82a23ad731308ff1db317076b0abb5 | |
| parent | 5fb5a0287f471dff37a691c37c730aa459b97dbb [diff] |
[syscalls] zx_pmt_unpin should always consume handle After this CL, zx_pmt_unpin always consumes its handle argument, even when the handle is the wrong type. ZX-2204 #comment Change-Id: I0ca107e4648840a0fcad7824537232f765db847c
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.