From: Pekka Enberg <penberg@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung.kim@lge.com>,
LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
David Ahern <dsahern@gmail.com>,
Stephane Eranian <eranian@google.com>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH 8/9] perf report: Add report.percent-limit config variable
Date: Thu, 16 May 2013 10:34:51 +0300 [thread overview]
Message-ID: <51948C1B.20408@kernel.org> (raw)
In-Reply-To: <8761yk5zdr.fsf@sejong.aot.lge.com>
On 05/15/2013 01:08 PM, Namhyung Kim wrote:
> Hi Pekka,
>
> On Tue, 14 May 2013 14:05:38 +0300, Pekka Enberg wrote:
>> On Tue, May 14, 2013 at 5:09 AM, Namhyung Kim <namhyung@kernel.org> wrote:
>>> From: Namhyung Kim <namhyung.kim@lge.com>
>>>
>>> Now an user can set a default value of --percent-limit option into the
>>> perfconfig file.
>>>
>>> $ cat ~/.perfconfig
>>> [report]
>>> percent-limit = 0.1
>>>
>>> Cc: Andi Kleen <andi@firstfloor.org>
>>> Cc: Pekka Enberg <penberg@kernel.org>
>>> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
>>
>> I'm not totally convinced this is useful. The limit is about "what is
>> significant" and that depends on what you are trying to measure.
>> There's an (absolute) lower limit somewhere between 0.1 and 1.0 but I
>> think we can just pick a reasonable default and let people use the
>> command line switch if they want to override it.
>
> If the limit depends on what is measured, what should be the reasonable
> default value? I just don't know..
>
> I agree that we should pick a default but the config variable doesn't
> harm anything in this case too. Some users might not agree with our
> default for their cases and want to use other value.
>
> But I'm not insist on it so strongly, I just gave another way.. ;)
I'd go for default value of 1.0 first and if people complain, drop it to
0.1. But I guess it's safer to add your config option thingy just in case:
Acked-by: Pekka Enberg <penberg@kernel.org>
Pekka
next prev parent reply other threads:[~2013-05-16 7:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 2:08 [PATCHSET 0/9] perf tools: Assorted fixes and changes on perf top/report Namhyung Kim
2013-05-14 2:08 ` [PATCH 1/9] perf top: Fix -E option behavior Namhyung Kim
2013-05-17 14:21 ` Jiri Olsa
2013-05-31 11:34 ` [tip:perf/core] " tip-bot for Namhyung Kim
2013-05-14 2:09 ` [PATCH 2/9] perf top: Fix percent output when no samples collected Namhyung Kim
2013-05-17 14:22 ` Jiri Olsa
2013-05-31 11:35 ` [tip:perf/core] " tip-bot for Namhyung Kim
2013-05-14 2:09 ` [PATCH 3/9] perf top: Get rid of *_threaded() functions Namhyung Kim
2013-05-17 14:28 ` Jiri Olsa
2013-05-31 11:37 ` [tip:perf/core] " tip-bot for Namhyung Kim
2013-05-14 2:09 ` [PATCH 4/9] perf hists: Move locking to its call-sites Namhyung Kim
2013-05-17 14:39 ` Jiri Olsa
2013-05-31 11:38 ` [tip:perf/core] " tip-bot for Namhyung Kim
2013-05-14 2:09 ` [PATCH 5/9] perf report: Don't be bothered with locking when adding hist entries Namhyung Kim
2013-05-17 14:39 ` Jiri Olsa
2013-05-31 11:39 ` [tip:perf/core] perf report: Don' t bother " tip-bot for Namhyung Kim
2013-05-14 2:09 ` [PATCH 6/9] perf report: Add --percent-limit option Namhyung Kim
2013-05-31 11:40 ` [tip:perf/core] " tip-bot for Namhyung Kim
2013-05-14 2:09 ` [PATCH 7/9] perf top: " Namhyung Kim
2013-05-31 11:42 ` [tip:perf/core] " tip-bot for Namhyung Kim
2013-05-14 2:09 ` [PATCH 8/9] perf report: Add report.percent-limit config variable Namhyung Kim
2013-05-14 11:05 ` Pekka Enberg
2013-05-15 10:08 ` Namhyung Kim
2013-05-16 7:34 ` Pekka Enberg [this message]
2013-05-31 11:43 ` [tip:perf/core] " tip-bot for Namhyung Kim
2013-05-14 2:09 ` [PATCH 9/9] perf top: Reuse " Namhyung Kim
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=51948C1B.20408@kernel.org \
--to=penberg@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.