Rodrigo Arias
70891355ec
The running task is inferred from the task on top of the stack. Also, allow a nested task to execute when there are others in the stack. |
||
---|---|---|
cfg | ||
doc | ||
nix | ||
test | ||
.gitignore | ||
.gitlab-ci.yml | ||
chan.c | ||
chan.h | ||
CMakeLists.txt | ||
common.h | ||
compat.h | ||
COPYING | ||
dump.c | ||
emu_kernel.c | ||
emu_nodes.c | ||
emu_nosv.c | ||
emu_openmp.c | ||
emu_ovni.c | ||
emu_tampi.c | ||
emu.c | ||
emu.h | ||
heap.h | ||
ovni2prv.c | ||
ovni.c | ||
ovni.h | ||
ovnisync.c | ||
parson.c | ||
parson.h | ||
pcf.c | ||
pcf.h | ||
plot-drift.py | ||
prv.c | ||
prv.h | ||
README.txt | ||
sort.c | ||
test_speed.c | ||
trace.c | ||
trace.h | ||
uthash.h | ||
utlist.h |
ovni - Obtuse but Versatile nOS-V Instrumentation The ovni instrumentation project is composed of a runtime library (libovni.so), which generates a fast binary trace, and post-processing tools such as the emulator (emu), 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, take a look at the doc/ directory. To build ovni you would need a C compiler, MPI and cmake version 3.10 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.