commit | e508992f44bbab11733431e96c7bc06d69e74231 | [log] [tgz] |
---|---|---|
author | Gianfranco Valentino <gevalentino@google.com> | Mon Dec 03 18:20:38 2018 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Dec 04 19:17:50 2018 +0000 |
tree | 5f5e5766e72f34d09a5aa4a247798bdc6f4b5a5f | |
parent | 3110a809b6c12469711b4f25346d2630f53ab297 [diff] |
[cobalt-client] Provide host dummy impl. Most of the users don't need host implementation, but those who do, would end up wrapping every statement in ifdef declarations. To avoid that provide a host compatible version, which essentially does nothing, uses a dummy implementation of Logger. User still need to wrap zircon specific code, but that is limited to the options for initialization. (zx::vmo, zx::duration). TEST=cobalt-client-tests Change-Id: Ic7defb847e721687ca4a2142af007ed0483f9c76
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.