Rodrigo Arias
2961254838
The region of past events must be enclosed by the OU[ and OU] events and all the events within the region must be sorted. The sorting mechanism looks back up to 10000 events, so it may fail if they are too far away in the past. |
||
---|---|---|
cfg | ||
doc | ||
test | ||
.gitignore | ||
chan.c | ||
chan.h | ||
CMakeLists.txt | ||
common.h | ||
COPYING | ||
dump.c | ||
emu_nanos6.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: % cmake -DCMAKE_INSTALL_PREFIX=$prefix -S . -B build % cd build % 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.