commit | 8a99a877cfa38a3137f47ee838cb7165c881c32f | [log] [tgz] |
---|---|---|
author | Nick Maniscalco <maniscalco@google.com> | Fri Jun 29 08:35:20 2018 -0700 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Jul 02 15:50:06 2018 +0000 |
tree | a16d280c4434d9a23a516fa2048f244feb0fcff8 | |
parent | 1cf2b7d2d26cd320bc39585854d8b1ca5b8cdf4d [diff] |
[hypervisor][x86] Use zx_time_t in update_timer Change update_timer declaration to accept zx_time_t instead of uint64_t. The function definition already accepts zx_time_t. In the future zx_time_t will change from uint64_t to int64_t. Tested: untested ZX-2100 #comment progress Change-Id: I1d4760237bfe01cc197047308154d85b1c3093fe
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.