WIP(dispatcher-isolate): Dispatchers in userspace

Would really help with unit testing

Can currently instatiate (with stubs)
  - ChannelDispatcher
  - EventDispatcher
  - Handle
  - StateTracker

Change-Id: I478374e16682aaecc7b7750c710b83a686fd067c
9 files changed
tree: 9037318eccac992c12a382872280cfeccd2b0a65
  1. .clang-format
  2. .dir-locals.el
  3. .gitignore
  4. .travis.yml
  5. AUTHORS
  6. LICENSE
  7. PATENTS
  8. README.md
  9. bootloader/
  10. docs/
  11. kernel/
  12. make/
  13. makefile
  14. navbar.md
  15. prebuilt/
  16. scripts/
  17. system/
  18. third_party/
README.md

Zircon

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.