| commit | d59312c53bbd613501609c7067b186c61b04fbee | [log] [tgz] |
|---|---|---|
| author | Brian Swetland <swetland@google.com> | Tue May 15 15:25:29 2018 -0700 |
| committer | Mike Voydanoff <voydanoff@google.com> | Wed May 16 14:33:45 2018 -0700 |
| tree | 204df180d564484c58289963843c588d1dba4359 | |
| parent | c42d7891b15e3721e6975b53338f3dae52c74b7d [diff] |
[ulib][kvstore] simple binary small key/value storage container Provide a container for storage of small (less than 256 byte) key/value pairs, intended for passing configuration/version state between bootloaders and running systems (at least initially) via the sys-config partition or other transports. Change-Id: I8c8159eb6199e93816d843fdbbb2fb374e002d77
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.