commit | 99b1a56ebcbdf44c9ddcc56bef3c0ad625fca451 | [log] [tgz] |
---|---|---|
author | Sean Klein <smklein@google.com> | Thu Nov 29 21:23:45 2018 -0800 |
committer | Sean Klein <smklein@google.com> | Sat Dec 08 04:58:01 2018 +0000 |
tree | 1f141aa7b1534d22c9d079eb0c384f7a1fb910c2 | |
parent | bc809d2b8d96c19be03f29889bc33715435bfb19 [diff] |
[block] Re-write the core block driver in safe C++ This enables: - RAII wrappers around handles, memory. - DDKTL usage, to avoid casting between "void*". - Automatically initialized mutexes. - Lock thread-annotations for safety. In the future, this will also enable improved encapsulation of the BlockDevice object, but structural changes have been minimized for the current patch. Test: /boot/test/sys/ramdisk-test Change-Id: Id041bd4cc5f541620e4829427fac3c964700b13b
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.