| commit | 27a3543a52cc95363ecec13c078aecb24958f322 | [log] [tgz] |
|---|---|---|
| author | Scott Graham <scottmg@google.com> | Wed Dec 05 14:33:08 2018 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Dec 10 21:36:11 2018 +0000 |
| tree | dfd1b26ab407f98bd6da42330a5a7799b7b17b91 | |
| parent | 32b0ab5a38deb1fc863cda90992d057a732c7325 [diff] |
[counters] Support a "max" mode for kcounters This adds a new mode for kcounters that treats the value as a maximum across cores, rather than a sum. These are declared with KCOUNTER_MAX() and modified with kcounter_max(). Additionally, adds two new max counters, one for live handles, and one for maximum allocation size in cmpct_alloc(). In implementing this I noticed that I think `kernel.handles.live` probably doesn't do quite what it wishes it was doing (maybe?) and filed ZX-3015. ZX-3092 #comment [counters] Support a "max" mode for kcounters ZX-3105 #comment [counters] Support a "max" mode for kcounters Test: CQ, manual inspection of `k counters view` Change-Id: I556fe74dfcb54e1fd61421fb13b6be65d4687243
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.