Skip to content

Changes

Page history
Updated Build (markdown) authored by Thomas Roehl's avatar Thomas Roehl
Show whitespace changes
Inline Side-by-side
Build.md
View page @ 3f7184ec
......@@ -24,7 +24,7 @@ Usually the only thing you have to configure is the `PREFIX` install path in the
## Changing color of [[likwid-pin|likwid-pin]] output
Depending on the background of your terminal window you can choose a color
for [[likwid-pin|likwid-pin]] output.
for [[likwid-pin|likwid-pin]] output. It can be set in the build config file `config.mk` at the variable `COLOR`. Possible colors are: `NONE`, `BLACK`, `RED`, `GREEN`, `YELLOW`, `BLUE`, `MAGENTA`, `CYAN` or `WHITE`.
## Usage of access daemon [[likwid-accessD|likwid-accessD]]
......@@ -39,14 +39,14 @@ To enable using the access daemon, configure in `config.mk`:
`ACCESSMODE` can be `direct`, `accessdaemon` and `sysdaemon` (not yet officially supported).
You can overwrite the default setting on the command line with the `-M` commandline option.
If you want to access Uncore performance counters that are located in the PCI memory range, like they are implemented in Intel SandyBridge EP and IvyBridge EP, you have to use the access daemon or have root privileges because access to the PCI space is only permitted for highly privileged users.
If you want to access Uncore performance counters that are located in the PCI memory range, like they are implemented in Intel SandyBridge EP and IvyBridge EP and newer architectures, you have to use the access daemon or have root privileges because access to the PCI space is only permitted for high privileged users.
## Usage of frequency daemon [[likwid-setFreq|likwid-setFreq]]
The application [[likwid-setFrequencies|likwid-setFrequencies]] uses another daemon to modify the frequency of CPUs. The daemon is build and later installed if `BUILDFREQ` is set to `true` in `config.mk`.
## Build LIKWID as shared library
Per default the LIKWID library is build as a shared library. You need the library if you want to use the Marker API. You can also use the LIKWID modules like `perfmon` directly. This is not officially supported at the moment. In some settings it is necessary to build LIKWID as a shared library. To do so set `SHARED_LIBRARY` to `true` in `config.mk`.
Per default the LIKWID library is build as a shared library. You need the library if you want to use the Marker API. You can also use the LIKWID modules like `perfmon` directly. In some settings it is necessary to build LIKWID as a shared library. To do so set `SHARED_LIBRARY` to `true` in `config.mk`.
## Instrument [[likwid-bench|likwid-bench]] for usage with [[likwid-perfctr|likwid-perfctr]]
......