Rodrigo Arias
505245d54c
The marks are parsed from the metadata definition, then merged from all threads and a new channel for each mark type is created. The channel type is specified using a flag when calling ovni_mark_type(), so the channels is set to single or stack. For now, only ovni_mark_push() and ovni_mark_pop() are implemented. |
||
|---|---|---|
| .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.