| commit | 705cdc55f2296650f8cc7590f3332b36b3356faf | [log] [tgz] |
|---|---|---|
| author | Tricia Landers <planders@google.com> | Fri Dec 07 13:03:43 2018 -0800 |
| committer | Tricia Landers <planders@google.com> | Mon Dec 10 14:45:13 2018 -0800 |
| tree | 63dfa5984e69b9c9462b945acf446bdc3b67ba5b | |
| parent | 9761712e43c65ec441b4abcf688059ef5cc084e8 [diff] |
[fvm] [host] Refactor fvm host-side tool 1. Separate FvmInfo and SparsePaver into their own files. 2. Rename fvm-lz4 to sparse-reader. 3. Rename partition_info_t structs to reflect which type of container they should be used with (Sparse or Fvm). Test: host-side fvm-test Change-Id: I6554814cf366422c824d6cf9dbbdd430ac2d7c4b
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.