| commit | 2fc7a810be83f376ceb392276985dcbc70389299 | [log] [tgz] |
|---|---|---|
| author | Marty Faltesek <mfaltesek@google.com> | Thu Dec 13 15:12:24 2018 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Jan 15 23:37:28 2019 +0000 |
| tree | b0082626751c5bfc0327d04db9b6e18e876f0de1 | |
| parent | 77e1d16d895b7effdb636bd624d3aacdffae8f82 [diff] |
[virtcon] Remove uses of port_wait_repeating() in system/core/virtcon. This is a step towards removing ZX_WAIT_ASYNC_REPEATING. Handlers registered with port_wait_repeating() would previously return an error status ZX_ERR_NEXT to prevent re-registering the repeating wait. When using port_wait(), handlers should return ZX_OK instead, to re-register the non-repeating wait. Previously when a key was released the timer was effectively disabled utilizing the ZX_TIME_INFINITE flag between vc_input_cb() and vc_timer_cb(). With this change, it is now explicitly disabled with zx_timer_cancel(), so place that in vc_input_cb() where key release is first detected. ZX-3090 Test: Verified console logging and key repeating works on pixelbook. Change-Id: Iaabb3804dbc51d69e07902840ad0ed7a1f5ef4aa
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.