[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151118000306.GD7062@sejong>
Date: Wed, 18 Nov 2015 09:03:06 +0900
From: Namhyung Kim <namhyung@...nel.org>
To: Taeung Song <treeze.taeung@...il.com>
CC: Arnaldo Carvalho de Melo <acme@...nel.org>,
linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
Jiri Olsa <jolsa@...hat.com>
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@...hat.com>
> Signed-off-by: Taeung Song <treeze.taeung@...il.com>
Acked-by: Namhyung Kim <namhyung@...nel.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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists