| ... | @@ -123,7 +123,10 @@ sudo setcap cap_sys_rawio+ep EXECUTABLE |
... | @@ -123,7 +123,10 @@ sudo setcap cap_sys_rawio+ep EXECUTABLE |
|
|
This is only possible on local file systems. A feasible way is to use the [[likwid-accessD|likwid-accessD]] for all accesses and just enable the capabilities for this one binary. This will enable the usage for all LIKWID tools and also for all instrumented binaries. If the [[likwid-perfctr|likwid-perfctr]] utility should only be used in wrapper mode, it is suitable to set the capabilities for [[likwid-perfctr|likwid-perfctr]] only. Please remember to set the file permission of the MSR device file to read/write for all users, even if capabilites are configured correctly.
|
|
This is only possible on local file systems. A feasible way is to use the [[likwid-accessD|likwid-accessD]] for all accesses and just enable the capabilities for this one binary. This will enable the usage for all LIKWID tools and also for all instrumented binaries. If the [[likwid-perfctr|likwid-perfctr]] utility should only be used in wrapper mode, it is suitable to set the capabilities for [[likwid-perfctr|likwid-perfctr]] only. Please remember to set the file permission of the MSR device file to read/write for all users, even if capabilites are configured correctly.
|
|
|
|
|
|
|
|
|
|
|
|
|
# Installation on Intel Xeon Phi
|
|
# Installation on Intel Xeon Phi (KNC)
|
|
|
In order to build LIKWID for the Xeon Phi, set the `COMPILER` option in config.mk to `MIC` and build it on a host that has a MIC-aware Intel compiler and the MPSS installed. Moreover, there might be the problem that the required Intel libraries are not present on the Xeon Phi and you need to copy them. Commonly the libraries are `libimf.so`, `libsvml.so`, `libirng.so` and `libintlc.so.5`. LIKWID assumes that they are copied in the same path as the LIKWID library `liblikwid.so` (`$INSTALLED_PREFIX/lib`). If you install them somewhere different, please set the `RPATHS` variable in config.mk or make/include_MIC.mk to point to the location.
|
|
In order to build LIKWID for the Xeon Phi, set the `COMPILER` option in config.mk to `MIC` and build it on a host that has a MIC-aware Intel compiler and the MPSS installed. Moreover, there might be the problem that the required Intel libraries are not present on the Xeon Phi and you need to copy them. Commonly the libraries are `libimf.so`, `libsvml.so`, `libirng.so` and `libintlc.so.5`. LIKWID assumes that they are copied in the same path as the LIKWID library `liblikwid.so` (`$INSTALLED_PREFIX/lib`). If you install them somewhere different, please set the `RPATHS` variable in config.mk or make/include_MIC.mk to point to the location.
|
|
|
|
|
|
|
|
Moreover, the Intel Xeon Phi has some limit of running processes and since every CPU needs its access daemon, LIKWID would start many processes. Therefore, LIKWID allows only direct access to the MSR device files on Xeon Phi. In order to allow this, set the suid-root bit for the Lua interpreter (`sudo chmod u+s $INSTALLED_PREFIX/bin/likwid-lua`).
|
|
Moreover, the Intel Xeon Phi has some limit of running processes and since every CPU needs its access daemon, LIKWID would start many processes. Therefore, LIKWID allows only direct access to the MSR device files on Xeon Phi. In order to allow this, set the suid-root bit for the Lua interpreter (`sudo chmod u+s $INSTALLED_PREFIX/bin/likwid-lua`).
|
|
|
|
|
|
|
|
# Installation on Intel Xeon Phi (KNL)
|
|
|
|
The successor of the KNC has more similarities with normal system CPUs. Therefore, no special compiler flags are needed during the build process, the default compiler `GCC` can be used. The only thing that needs to be adjusted is the number of supported hardware threads. In `config.mk` the variable `MAX_NUM_THREADS` must be at least the number of hardware threads, so for a 72 core KNL you have to set the variable to minimum 288. |
|
|
|
\ No newline at end of file |
