commit | b26eac05e1868b3b8edd89cc7dfa846229e71559 | [log] [tgz] |
---|---|---|
author | Aaron Green <aarongreen@google.com> | Fri Sep 14 18:20:09 2018 -0700 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Sep 20 19:30:31 2018 +0000 |
tree | 0422538c65e6178313d5f1c1258b1ced04f0f679 | |
parent | 88958d7480fad7a2323a775f54d79c0d24110a4b [diff] |
[fuzz] Add component manifest handling This CL updates the fuzz tool to use component manifests when fuzzing Fuchsia packages. This allows fuzz targets to be linked dynamically against their sanitized dependencies at runtime. It also updates the test fixture with fake component manifests. SEC-103 Tests: Updated unit tests to use component manifests Change-Id: I49bd35535bf6605c0a60e28d2ce064b6cfec6e91
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.