|author||Namhyung Kim <email@example.com>||2015-12-15 10:49:56 +0900|
|committer||Arnaldo Carvalho de Melo <firstname.lastname@example.org>||2015-12-15 11:46:16 -0300|
perf record: Add record.build-id config option
Post processing at 'perf record' takes a long time on big machines. What it does is to find the build-id of binaries found in the event stream, so that it can make sure, at 'report' time, that the symtabs (be it ELF, kallsyms, etc) being used to resolve symbols are the ones matching the binaries found at 'record' time. Sometimes we just want to skip this processing of events at the end of the session to get quicker results, making sure the binaries haven't changed from 'record' to 'report' time. Add a new config option to control this behavior. The record.build-id config variable can have one of the following values: - cache: post-process data and save/update the binaries into the build-id cache (in ~/.debug). This is the default. - no-cache: post-process the data but not update the build-id cache. Same effect as using the -N option. - skip: skip post-processing and do not update the cache. Same effect as using the -B option. Reported-and-Acked-by: Peter Zijlstra (Intel) <email@example.com> Signed-off-by: Namhyung Kim <firstname.lastname@example.org> Acked-by: Jiri Olsa <email@example.com> Cc: David Ahern <firstname.lastname@example.org> Cc: Taeung Song <email@example.com> Link: http://firstname.lastname@example.org [ Added some more text to the documentation ] Signed-off-by: Arnaldo Carvalho de Melo <email@example.com>
Diffstat (limited to 'tools/perf/Documentation')
1 files changed, 13 insertions, 1 deletions
diff --git a/tools/perf/Documentation/perf-record.txt b/tools/perf/Documentation/perf-record.txt
index 8d032f4e50bf..3a1a32f5479f 100644
@@ -207,11 +207,23 @@ comma-separated list with no space: 0,1. Ranges of CPUs are specified with -: 0-
In per-thread mode with inheritance mode on (default), samples are captured only when
the thread executes on the designated CPUs. Default is to monitor all CPUs.
+Do not save the build ids of binaries in the perf.data files. This skips
+post processing after recording, which sometimes makes the final step in
+the recording process to take a long time, as it needs to process all
+events looking for mmap records. The downside is that it can misresolve
+symbols if the workload binaries used when recording get locally rebuilt
+or upgraded, because the only key available in this case is the
+pathname. You can also set the "record.build-id" config variable to
+'skip to have this behaviour permanently.
Do not update the buildid cache. This saves some overhead in situations
where the information in the perf.data file (which includes buildids)
+is sufficient. You can also set the "record.build-id" config variable to
+'no-cache' to have the same effect.