Skip to content

Changes

Page history
Updated EnvVariables (markdown) authored by Thomas Gruber's avatar Thomas Gruber
Show whitespace changes
Inline Side-by-side
EnvVariables.md
View page @ 7640a78b
......@@ -3,6 +3,7 @@
Some functionality of the LIKWID library can be changed by setting environment variables. Here is a list of variables used by LIKWID:
* `LIKWID_FORCE`: Enables the overwriting of counters that are detected to be in-use. The environment variable is similar to the `-f`/`--force` command line switch for `likwid-perfctr`
* `LIKWID_NO_ACCESS`: The execution does not require the access layer (access to hardware counters). For example, this variable is set by `likwid-topology` or `likwid-pin`
* `LIKWID_PIN`: The comma-separated list contains the CPUs the application threads should be pinned to. Careful, the first CPU in the cpuset must be the last entry because the application is pinned to this CPU per default.
* `LIKWID_SILENT`: Disable stdout output caused by the library and the scripts. Some scripts provide the `-q`/`--quiet` command line switch which provides the same functionality
* `LIKWID_SKIP`: Variable content must be a hexmask. This hexmask describes which threads should be skipped while pinning. This function is required to avoid pinning the shepherd threads used by some OpenMP and MPI implementations. The version 4.3.1 introduced an automatic detection of the shepherd threads. In most cases the detection works, but if not, the hexmask overwrites the automatic detection.
* `LIKWID_DEBUG`: Verbosity settings for the LIKWID library
......@@ -14,7 +15,6 @@ Some functionality of the LIKWID library can be changed by setting environment v
* `LIKWID_DEBUG`: Verbosity settings for the LIKWID library
* `LIKWID_EVENTS`: Event string or performance group name. Multiple event strings or performance group names can be separated by `|`
* `LIKWID_THREADS`: The CPUs LIKWID is configured to run on (comma-separated list)
* `LIKWID_PIN`: The comma-separated list contains the CPUs the application threads should be pinned to. Careful, the first CPU in the cpuset must be the last entry because the application is pinned to this CPU per default.
## Environment variables used by the LIKWID library which access mode `perf_event`
......