mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Ingo Molnar <mingo@kernel.org>, Paul Mackerras <paulus@samba.org>,
	Namhyung Kim <namhyung.kim@lge.com>,
	LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH 8/8] perf symbol: Don't demangle parameters and such by default
Date: Tue, 12 Aug 2014 16:17:01 +0900	[thread overview]
Message-ID: <87egwmfa8i.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20140811133223.GC3277@kernel.org> (Arnaldo Carvalho de Melo's message of "Mon, 11 Aug 2014 10:32:23 -0300")

Hi Arnaldo,

On Mon, 11 Aug 2014 10:32:23 -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Aug 11, 2014 at 05:17:37PM +0900, Namhyung Kim escreveu:
>> On Sat, 2 Aug 2014 10:35:03 -0300, Arnaldo Carvalho de Melo wrote:
>> > Em Thu, Jul 31, 2014 at 02:47:42PM +0900, Namhyung Kim escreveu:
>> >> Some C++ symbols have very long name and they make column length
>> >> longer.  Most of them are about parameters including templates and we
>> >> can ignore such info most of time IMHO.
>
>> >> This patch passes DMGL_NO_OPTS by default when calling bfd_demangle().
>> >> One can still see full symbols with -v/--verbose option.
>
>> >> before:
>> >>   JS_CallFunctionValue(JSContext*, JSObject*, JS::Value, unsigned int, JS::Value*, JS::Value*)
>
>> >> after:
>> >>   JS_CallFunctionValue
>
>> > Are you sure we want that?
>
>> > With this we'll end up having different instantiations having the same
>> > name, since the way to differentiate them is exactly by a different
>> > parameter list, no?
>> 
>> Right, but I think it's not a big problem since such overloaded
>> functions will not be shown at the same time as only one of them might
>> do the real work most cases.  Simply noticing one of them is a
>
> But then only someone that has deep knowledge of the code in question
> will figure that out from just the function name.
>
> A way to toggle that, starting with a sane value, in this case probably
> not showing the parameter listing due to it being overly long would be
> ideal.
>
> Perhaps I can process this patch now and leave this toggling of things
> that --verbose shows to a second patchset, where this and
> --show-total-period, --show-nr-samples, --hide-unresolved, even
> annotation stuff needs to be on-the-fly togglable, like
> --disassembly-style.
>
>> performance bottle neck would be helpful to the developer, I guess.
>> Even if it's not the case, one still can see and identify the correct
>> one using the -v option.
>  
>> For me, it's just annoying when (unimportant) C++ symbols occupy too
>> much space in a limited terminal width.
>
> What is annoying/unimportant to a person may be the missing detail for
> someone else.
>
> Not having to restart a possibly long top/report session from scratch
> looks like a nice feature to have.
>
> I'll take the patch, its just one more thing that gets in the --verbose
> grab bag till we make all on-the-fly togglable.

Thanks, I'll think about the toggling later. :)

Thanks,
Namhyung

  reply	other threads:[~2014-08-12  7:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31  5:47 [PATCHSET 0/8] perf tools: Honor column width setting (v3) Namhyung Kim
2014-07-31  5:47 ` [PATCH 1/8] perf tools: Left-align output contents Namhyung Kim
2014-08-13  5:17   ` [tip:perf/core] " tip-bot for Namhyung Kim
2014-07-31  5:47 ` [PATCH 2/8] perf tools: Make __hpp__fmt() receive an additional len argument Namhyung Kim
2014-08-02 13:30   ` Arnaldo Carvalho de Melo
2014-08-11  8:05     ` Namhyung Kim
2014-08-11 13:17       ` Arnaldo Carvalho de Melo
2014-08-12  7:13         ` Namhyung Kim
2014-08-13  5:18   ` [tip:perf/core] " tip-bot for Namhyung Kim
2014-07-31  5:47 ` [PATCH 3/8] perf tools: Save column length in perf_hpp_fmt Namhyung Kim
2014-08-13  5:18   ` [tip:perf/core] " tip-bot for Namhyung Kim
2014-07-31  5:47 ` [PATCH 4/8] perf report: Honor column width setting Namhyung Kim
2014-08-13  5:18   ` [tip:perf/core] " tip-bot for Namhyung Kim
2014-07-31  5:47 ` [PATCH 5/8] perf top: Add -w option for setting column width Namhyung Kim
2014-08-13  5:18   ` [tip:perf/core] " tip-bot for Namhyung Kim
2014-07-31  5:47 ` [PATCH 6/8] perf tools: Add name field into perf_hpp_fmt Namhyung Kim
2014-08-13  5:19   ` [tip:perf/core] " tip-bot for Namhyung Kim
2014-07-31  5:47 ` [PATCH 7/8] perf tools: Fix column alignment when headers aren't shown on TUI Namhyung Kim
2014-08-13  5:19   ` [tip:perf/core] " tip-bot for Namhyung Kim
2014-07-31  5:47 ` [PATCH 8/8] perf symbol: Don't demangle parameters and such by default Namhyung Kim
2014-08-02 13:35   ` Arnaldo Carvalho de Melo
2014-08-11  8:17     ` Namhyung Kim
2014-08-11 13:32       ` Arnaldo Carvalho de Melo
2014-08-12  7:17         ` Namhyung Kim [this message]
2014-08-14  8:49   ` [tip:perf/core] perf symbols: Don' t " tip-bot for 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=87egwmfa8i.fsf@sejong.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung.kim@lge.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome