Rodrigo Arias
93ab5a5833
In order to allow easy debugging of some programs and runtimes, it is often neccessary to add extra information in the timeline views. The modification of the emulator to accomodate those temporal events is time consuming and requires knowlegde of the emulator internals. To improve the situation, a new set of functions are added to libovni which allow users to define their own views. Up to 100 types of events can be declared, where each type can have an unlimited number ov values with an optional label attached. |
||
|---|---|---|
| .gitea/workflows | ||
| cfg | ||
| cmake | ||
| doc | ||
| include | ||
| src | ||
| test | ||
| .clang-format | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .readthedocs.yaml | ||
| CHANGELOG.md | ||
| CMakeLists.txt | ||
| COPYING | ||
| flake.lock | ||
| flake.nix | ||
| mkdocs.yml | ||
| README.md | ||
The ovni project is composed of a runtime library (libovni.so), which generates a fast binary trace, and post-processing tools such as the emulator ovniemu, which transform the binary trace to the PRV format, suitable to be loaded in Paraver.
The libovni.so library is licensed under MIT, while the rest of tools are GPLv3 unless otherwise stated.
For more information, read the documentation online or take a look at the
doc/ directory. You can display the documentation in HTML by running mkdocs serve from the root directory.
To build ovni you would need a C compiler, MPI and cmake version 3.20 or newer.
To compile in build/ and install into $prefix use:
$ mkdir build
$ cd build
$ cmake -DCMAKE_INSTALL_PREFIX=$prefix ..
$ make
$ make install
To run the tests you can run (from the build directory):
$ make test
See cmake(1) and cmake-env-variables(7) to see more information about the variables affecting the generation and build process.