commit | 1af5c2c5d9db011b5e5dfec1fc21018713b0c2f3 | [log] [tgz] |
---|---|---|
author | Yifei Teng <yifeit@google.com> | Thu Jan 24 15:16:16 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Jan 28 21:16:34 2019 +0000 |
tree | b26aa400220168f084081efaf895f7599a022de3 | |
parent | d618cc58ce087274b3644c25332dc2c0d433fcdf [diff] |
[fidl][llcpp] Unit-testing non-simple FIDL messages Since the llcpp server implementation is not yet ready, for this patch, a simple manual server is written that takes advantage of the raw llcpp APIs and acts as the testing harness for llcpp client code. The garnet CL used to generate the binding code is at: https://fuchsia-review.googlesource.com/c/garnet/+/239196 TEST: /boot/test/sys/fidl-llcpp-interop Change-Id: I960a3282b9f74506f2a5ffafaa3ece6fa6377c69
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
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.