Messages in this thread | | | Date | Wed, 18 Nov 2015 09:03:06 +0900 | From | Namhyung Kim <> | Subject | Re: [PATCH v11 05/24] perf config: Document 'buildid.dir' variable in man page |
| |
On Tue, Nov 17, 2015 at 10:53:25PM +0900, Taeung Song wrote: > Explain 'buildid.dir' variable. > > Cc: Jiri Olsa <jolsa@redhat.com> > Signed-off-by: Taeung Song <treeze.taeung@gmail.com>
Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks, Namhyung
> --- > 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 ec30229..b4ee205 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 >
| |