Explain 'buildid.dir' variable.
Cc: Namhyung Kim <namhy...@kernel.org>
Cc: Jiri Olsa <jo...@redhat.com>
Signed-off-by: Taeung Song <treeze.tae...@gmail.com>
---
tools/perf/Documentation/perf-config.txt | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/tools/perf/Documentation/perf-config.txt
b/tools/perf/Documentation/perf-config.txt
index 32eac14..ee98fca 100644
--- a/tools/perf/Documentation/perf-config.txt
+++ b/tools/perf/Documentation/perf-config.txt
@@ -151,6 +151,21 @@ tui.*, gtk.*::
By setting value, TUI or GTK can be enabled or not. But it is needed
that perf detects the required library for them during build.
+buildid.*::
+ buildid.dir::
+ Each executable and shared library in modern distributions
comes with a
+ content based identifier that, if available, will be inserted
in a
+ 'perf.data' file header to, at analysis time find what is
needed to do
+ symbol resolution, code annotation, etc.
+
+ The recording tools also stores a hard link or copy in a
per-user
+ directory, $HOME/.debug/, of binaries, shared libraries,
/proc/kallsyms
+ and /proc/kcore files to be used at analysis time.
+
+ The buildid.dir variable can be used to either change this
directory
+ cache location, or to disable it altogether. If you want to
disable it,
+ set buildid.dir to /dev/null. The default is $HOME/.debug
+
SEE ALSO
--------
linkperf:perf[1]
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
