| commit | 83df5def93293e07a2cb50d228de8125c173ff2d | [log] [tgz] |
|---|---|---|
| author | Christopher Anderson <cja@google.com> | Fri Jun 01 12:19:36 2018 -0700 |
| committer | Christopher Anderson <cja@google.com> | Fri Jul 20 13:51:15 2018 -0700 |
| tree | de14f221df3a09afa4283f72d255376e5d3b86e7 | |
| parent | 0755c1067caf7d089ee66ab70bce243e87e41ad0 [diff] |
[dev][platform-bus] Move MMIO/IRQ allocations to proxy devhosts Change pdev proxy drivers so that on creation they request resource handles for their MMIOs and IRQs from the platform bus. Use these resource handles to create the objects within the proxy devhost itself, and set the name of the vmos for better bookkeeping. This change integrates the PhysicalAspaceManager and exclusive resource allocation into the ARM platform. Change-Id: I8ea30c87a94952d0314f62a02ec6343bba37e03e
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.