commit | ea19967fa67c3ded65203914e0aee02e73b9806b | [log] [tgz] |
---|---|---|
author | Suraj Malhotra <surajmalhotra@google.com> | Thu Jan 17 11:21:31 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Jan 29 19:08:55 2019 +0000 |
tree | b0eda24e206c29b697be6e6f6fd7ebe978953498 | |
parent | 2d0ddc4468af26b568a1fa8ee9865b5fcc8d86ba [diff] |
[dev][operation] Add operation library This library provides a generic solution to the private section problem which exists for types such as usb_request_t, node_operation_t, block_opt_t, and others. Specialized wrappers for each of those types can be built on top this library. More specifically, the problem exists whereby a series of drivers reuse the same object as it traverses the driver stack for a specific subsystem. There exists a public section specified by a banjo protocol, along with a private section for each layer in driver stack appended to the end of it like so: --------------------- | Public Definition | --------------------- | Driver 1 Private | --------------------- | Driver 2 Private | --------------------- | ... | --------------------- | Driver N Private | --------------------- Driver N in this case would perform the allocation of the entire struct. Driver 1 in the example above would be the device driver which talks directly to hardware. The request would only be "owned" by a single driver at a time, but only Driver N (the one who allocated the request) would be allowed to free it. The library is inspired by the usb::Request and friends library. They will transition to being built on top of this library in future CLs. Tested: `runtests -t operation-test` Change-Id: I3ab6bdab14ef5f1654bde9817321286bf5e6eb36
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.