From 6b5c0cc57937bb2d69a2474dca3a8fd52ee71edc Mon Sep 17 00:00:00 2001
From: "Joachim Wuttke (o)" <j.wuttke@fz-juelich.de>
Date: Wed, 25 May 2016 16:09:38 +0200
Subject: [PATCH] Notes on Linux tool perf

---
 dev-tools/profiling/README | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/dev-tools/profiling/README b/dev-tools/profiling/README
index 369a841fc63..79558124daa 100644
--- a/dev-tools/profiling/README
+++ b/dev-tools/profiling/README
@@ -11,6 +11,7 @@ There are several ways of code profiling:
 ----------------------------------------------------------
 Profiling with valgrind
 ----------------------------------------------------------
+
 1) Compile BornAgain as usuall and simply run
 ./run_valgrind.sh
 
@@ -49,3 +50,14 @@ run_gperftools.sh
 ----------------------------------------------------------
 Profiling with perf
 ----------------------------------------------------------
+
+Under Linux.
+
+Install Debian package linux-perf.
+
+echo "-1" >/proc/sys/kernel/perf_event_paranoid
+
+perf stat <any performance test>
+
+perf record -o /tmp/perf.out <any performance test>
+perf report -i /tmp/perf.out
-- 
GitLab