|author||George Kulakowski <email@example.com>||Fri Jan 11 16:51:45 2019 -0800|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Sat Jan 12 04:55:45 2019 +0000|
[abigen] Fix syscall generation for one argument and zero returns The computation of how many C arguments to include would underflow in the case that there were no abigen-level return values. This was not noticed, as the value was only compared to be greater than zero, and all existing syscalls with no return values have at least two abigen-level parameters. This was discovered by an experiment to make _zx_handle_close return void. As it then has one parameter and no return values, the underflow was observable. Test: manual inspection of out/.../syscalls/definitions.h Change-Id: I25a20a17fb939dbf069ae5e6ad132d3c70ccec99
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.