commit | 9eba95a2d7359e28993ca46b3682379c56d3a595 | [log] [tgz] |
---|---|---|
author | Sean Klein <smklein@google.com> | Sun Jan 06 16:34:39 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Sun Jan 27 22:10:32 2019 +0000 |
tree | 2b22835a2b8c99a11d5b45d5def75132d3fcb317 | |
parent | 688177673855a48d662517eb7bd0848d91b2b988 [diff] |
[ramdisk] Avoid usage of 'block' interface for accessing Ramdisk ioctls Additionally, redirects all usage of "ramdisk_ioctl" interfaces through the ramdisk library (currently located within ulib/fs-management, pending relocation). This will make it easier to convert the ioctl interfaces to FIDL without modifying client code. Test: /boot/test/sys/ramdisk-test ZX-2674 #comment In Progress Change-Id: Ia24192df10b2cb3bb5ee2a95f0b6ef647d515d69
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
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.