linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>,
	Taeung Song <treeze.taeung@gmail.com>
Subject: Re: [PATCH] perf record: Add record.build-id config option
Date: Tue, 15 Dec 2015 09:16:02 +0100	[thread overview]
Message-ID: <20151215081602.GA26506@krava.brq.redhat.com> (raw)
In-Reply-To: <1450144196-22957-1-git-send-email-namhyung@kernel.org>

On Tue, Dec 15, 2015 at 10:49:56AM +0900, Namhyung Kim wrote:
> Post processing at perf record takes long time on big machines.  What it
> does is to find build-id of related binaries.  Sometimes we just want to
> skip the processing and get the result quickly.  Add a new config option
> to control this behavior.
> 
> The record.build-id config variable can have one of following:
> 
>  - cache: post-process data and save/update the binaries into the
>           build-id cache (in ~/.debug).  This is default.
>  - no-cache: post-process data but not update the build-id cache.
>              Same effect with using -N option.
>  - skip: skip post-processing and not update the cache.
>          Same effect with using -B option.

Acked-by: Jiri Olsa <jolsa@kernel.org>

thanks,
jirka

  reply	other threads:[~2015-12-15  8:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15  1:49 [PATCH] perf record: Add record.build-id config option Namhyung Kim
2015-12-15  8:16 ` Jiri Olsa [this message]
2015-12-15 12:44 ` Peter Zijlstra
2015-12-15 14:41 ` Arnaldo Carvalho de Melo
2015-12-18  8:51 ` [tip:perf/core] " tip-bot for Namhyung Kim
2016-01-08  8:58   ` Taeung Song

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151215081602.GA26506@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=treeze.taeung@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).