commit | 5bb797f93e0d3af06f0a91eb870692db40e3d935 | [log] [tgz] |
---|---|---|
author | Fadi Meawad <fmeawad@google.com> | Thu Dec 06 14:14:12 2018 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jan 30 23:45:56 2019 +0000 |
tree | 710920f227100d60e8edd312acdcd79c804d152e | |
parent | b52c694036cc077b0fc7935d8e0b4181dbdd3bd5 [diff] |
[tracing] Reland "Make TRACE_DURATION use trace duration complete events" This is a reland of a3b4302f688a1b0c2d62d41883a4a44a465169fb This CL was reverted due to lack of support in measure. The measure library support was added in: https://fuchsia-review.googlesource.com/c/garnet/+/246312 TEST: The garnet-*-perf-* bot was failing before the support was added, but now it is green. PT-72 #done Original change's description: > [tracing] Make TRACE_DURATION use trace duration complete events > > ... instead of a start and end events. Saving ~50% in buffer and JSON > sizes. > > There is no noticeable change in performance for NTRACE, tracing > disabled, category disabled and tracing enabled. > > The compiled code size is less than or nearly equal the old version for 4 > or less arguments but it is bigger for 8 arguments and more, issue > tracked in PT-87. > > TEST: fx shell /system/test/sys/trace-test > TEST: fx shell trace-benchmark > > PT-72 #done Change-Id: I21510f2ffd1b7d79a622927bc999ce8cb9375396
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.