| commit | cbcc3007a71f77326d21f7232c32bfc18a574b69 | [log] [tgz] |
|---|---|---|
| author | Todd Eisenberger <teisenbe@google.com> | Wed Apr 04 16:11:17 2018 -0700 |
| committer | Todd Eisenberger <teisenbe@google.com> | Thu Apr 05 14:49:04 2018 -0700 |
| tree | fd3d70f817ee561dd5f54d4e2dc73d9f9452bcb4 | |
| parent | c4a811db86c22a6d1600f0de68a02e2d4c886e60 [diff] |
[syscalls][bti] Introduce zx_bti_clear_quarantine This allows BTI holders to clear out quarantined PMTs. This will generally be done by a driver after the device is initialized and its DMA systems quiesced. ZX-1936 #comment Introduce quarantine syscall Change-Id: Ic6bf132381f994607d02d987e0302f3c9cf3265b
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.