... | @@ -53,9 +53,11 @@ Per default the LIKWID library is build as a shared library. You need the librar |
... | @@ -53,9 +53,11 @@ Per default the LIKWID library is build as a shared library. You need the librar |
|
[[likwid-bench|likwid-bench]] is instrumented for use with [[likwid-perfctr|likwid-perfctr]]. This allows you to measure various metrics of your [[likwid-bench|likwid-bench]] kernels. Enable instrumentation by setting `INSTRUMENT_BENCH` to `true` in `config.mk`.
|
|
[[likwid-bench|likwid-bench]] is instrumented for use with [[likwid-perfctr|likwid-perfctr]]. This allows you to measure various metrics of your [[likwid-bench|likwid-bench]] kernels. Enable instrumentation by setting `INSTRUMENT_BENCH` to `true` in `config.mk`.
|
|
|
|
|
|
## Build LIKWID with perf_event backend instead of native access
|
|
## Build LIKWID with perf_event backend instead of native access
|
|
LIKWID can be built to run on top of `perf_event` (`USE_PERF_EVENT` in `config.mk`), an interface of the Linux kernel to the hardware performance monitors. The events and counters are the same but not all might be supported. The thermal and energy module are currently not supported with perf_event, most Uncore monitors are experimental.
|
|
LIKWID can be built to run on top of `perf_event` (`config.mk`: `USE_PERF_EVENT` in 4.2 and ACCESSMODE=perf_event in 4.3), an interface of the Linux kernel to the hardware performance monitors. The events and counters are the same but not all might be supported. The thermal module is currently not supported with perf_event, most Uncore monitors are experimental if they are provided by perf
|
|
For core-local measurements the paranoid level of 1 is enough to measure applications. To get the same behavior as native access, the paranoid level must be 0 or less. 0 or less is also required for Uncore measurements.
|
|
For core-local measurements the paranoid level of 1 is enough to measure applications. To get the same behavior as native access, the paranoid level must be 0 or less. 0 or less is also required for Uncore measurements.
|
|
|
|
|
|
|
|
Be aware that LIKWID reads information out of registers that is not provided by any other source like procfs and sysfs. When switching to perf_event backend, these registers cannot be accesseunrz139
|
|
|
|
|
|
## Enabling Fortran interface for Marker API
|
|
## Enabling Fortran interface for Marker API
|
|
|
|
|
|
If you want to use the Marker API in Fortran programs, LIKWID offers a native Fortran90 interface. To enable it, set `FORTRAN_INTERFACE` to `true` in `config.mk`. More information using LIKWID with Fortran look at [[Marker API with Fortran90|TutorialMarkerF90]].
|
|
If you want to use the Marker API in Fortran programs, LIKWID offers a native Fortran90 interface. To enable it, set `FORTRAN_INTERFACE` to `true` in `config.mk`. More information using LIKWID with Fortran look at [[Marker API with Fortran90|TutorialMarkerF90]].
|
... | | ... | |