| commit | 32adb6c0a7e9417b18acd5e6b212eff8142da620 | [log] [tgz] |
|---|---|---|
| author | Carlos Pizano <cpu@google.com> | Wed Jan 23 18:57:23 2019 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Jan 24 19:09:03 2019 +0000 |
| tree | b5b3ae73972f8cc09ba7265b944ccf9de62707cc | |
| parent | 8a9dc397e2a119d5f7f07a2955965db85914a944 [diff] |
[zircon][counters] remove kernel commands This continues the transition of the kernel counter functionality from ak" command to pure usermode. - Removes all query methods from kernel and the "k counters" command - Adds the basic 'watch' mode to the user app Things lost: - The printing in verbose mode was better in kernel - The Turkey fences-based detector and tests of same We can recover and better them as needed. Test= Manual, for example, print every 10 seconds the handle counters: $ kcounter -w10 kernel.ha watch mode every 10 seconds [1] kernel.handles.duped = 2169 kernel.handles.live = 2429 kernel.handles.made = 8715 kernel.handles.max_live = 712 [2] kernel.handles.duped = 2189 kernel.handles.live = 2431 kernel.handles.made = 8825 kernel.handles.max_live = 712 ZX-3010 #comment [zircon][counters] remove kernel commands Change-Id: I6cd867e7387efb8bd5d005d9e22768ad520ce96e
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.