| commit | 83dd7df7e71bb844a94903ef362c410122c6f81a | [log] [tgz] |
|---|---|---|
| author | Mark Seaborn <mseaborn@google.com> | Mon Mar 19 17:14:42 2018 -0700 |
| committer | Mark Seaborn <mseaborn@google.com> | Mon Mar 19 17:14:42 2018 -0700 |
| tree | 84d3d6eec828d96ba382c9614b4974de3fd700fd | |
| parent | d04ac15542dd027f317a99d3c285028a2d28deae [diff] |
[perftest] Add library for running performance tests This is approximately a port to Zircon of the perf test runner from garnet/bin/zircon_benchmarks/test_runner.cc. Changes from that include the following: * Use a KeepRunning() interface similar to gbenchmark so that the test function can own the loop. This is useful for test cases that need to return to an event loop. * Use a "bool" return type (rather than "void"), to allow propagating errors. This will eventually allow compatibility with unittest.h's ASSERT_*() macros, though these aren't supported with perftest yet. * This version has some unit tests for the perf test runner. * This version will print a table of summary statistics for the test cases. * This version mostly uses getopt_long() for command line argument parsing. In contrast, zircon_benchmarks uses the gflags library, which isn't available in the Zircon layer. * We leave out producing trace events for test runs for now. I'll add this back later. ZX-1715 Change-Id: I90d313b4223b4a0548b2edc32ad77b6e6de0310a
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.