commit | c88b358d552331cd5806e84017c77b659ec19cd4 | [log] [tgz] |
---|---|---|
author | Mark Seaborn <mseaborn@google.com> | Tue Nov 21 15:57:26 2017 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Nov 22 22:41:34 2017 +0000 |
tree | 8418df946f10676d501be92684abb0cbf9421d9c | |
parent | e6a85ea07ae35a48b84d049eca43785146420afe [diff] |
[kernel] Change callers of copy_from_user() to propagate its error code Change the call sites of copy_from_user() to propagate whatever error code it returned, instead of returning ZX_ERR_INVALID_ARGS. Currently copy_from_user() returns ZX_ERR_INVALID_ARGS on error, so this does not change the kernel's behaviour at all. However, it does mean that this error code is specified in fewer places. Change-Id: I9ba701461a8b53da00a202d20bebbdd569526fbb
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.