| commit | fd8500026ec556d5dcfe435e62c39f87b815f2e5 | [log] [tgz] |
|---|---|---|
| author | Pascal Perez <pascallouis@google.com> | Tue Dec 04 20:04:29 2018 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Dec 11 00:45:48 2018 +0000 |
| tree | 936fac57fde753e031fd1e803171c209ea461463 | |
| parent | 312b12489f721e204668f007af06554f0993eaf2 [diff] |
[fidlc] Start of type constraints - Defining schemas for attributes, which determine allowed placement, allowed values, and optionally carry a constraint - Instrumenting the compilation step to verify attributes' placement (moved from raw to ast conversion), verify attributes' values, and if placed correctly, verifies constraints - For interfaces, interpreting constraint as being applied to all methods, which itself is interpreted as being applied to the request and/or response struct - Moving the typo check to leverage the attribute schema database, so as to avoid having two places where we keep lists of all attributes supported - New test examplifying how type constraints are added, and ensuring mechanics work Test: make -j 72 HOST_USE_ASAN=true tools && ./build-x64/host_tests/fidl-compiler-test Change-Id: If8c8f2155e7b8cd5a5270f5a3a5ab49479f54f33
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.