| commit | 0f9088d6be016a0d2b5f1e426d0e3f13747010fd | [log] [tgz] |
|---|---|---|
| author | John Grossman <johngro@google.com> | Mon Jul 16 16:41:35 2018 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Aug 16 23:09:31 2018 +0000 |
| tree | 6cedce406456b5dd65697dc63d5c6ae0e700b75d | |
| parent | 42386fc14bb6e05f39f5a103d759c696323e97e9 [diff] |
[vmo-utils] Move PinnedVmo from IntelHDA utils into libfzl Promote the PinnedVmo class out of the IntelHDA driver and up to libfzl so that it can be used by other drivers. ZX-2462 #comment PinnedVmo class promoted into libfzl from HDA driver Test: Build and manual test with existing HDA driver. Change-Id: I60b2501c906e5ef3a58e9d6f1dc4ded6cfa3a191
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.