commit | a5a643f1dec05c42439ea3f6dfb8b26d8cbedcae | [log] [tgz] |
---|---|---|
author | Venkatesh Srinivas <venkateshs@google.com> | Tue Jan 29 05:20:21 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Jan 29 22:56:43 2019 +0000 |
tree | 55d2a26314d86e71b4fc1c207688bd194f011802 | |
parent | 3deb3c9cdaae6e90a51c5dafb3f01f71e603c3c9 [diff] |
[scsilib] Definitions for SCSI READ CAPACITY (16) command READ CAPACITY (16) is a service action of the SERVICE ACTION command. It reports the size of a block device's blocks and the number of blocks. ZX-2314 Tested: Built Change-Id: Id76096e8510e6b5653a99bcb5f51d1386e8cef66
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.