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: Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Borislav Petkov <bp@suse.de>,
	Brendan Gregg <brendan.d.gregg@gmail.com>,
	Chandler Carruth <chandlerc@gmail.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Stephane Eranian <eranian@google.com>,
	Wang Nan <wangnan0@huawei.com>
Subject: Re: [RFC/PATCH 3/3] perf tools: Defaults to 'caller' callchain order only if --children is enabled
Date: Fri, 23 Oct 2015 00:51:01 +0900	[thread overview]
Message-ID: <CAM9d7chC9FkdFYEDic8EU3QLEmrJsY2-vv9VTjSnS7FMmdqsUg@mail.gmail.com> (raw)
In-Reply-To: <20151022143704.GD2455@kernel.org>

On Thu, Oct 22, 2015 at 11:37 PM, Arnaldo Carvalho de Melo
<acme@kernel.org> wrote:
> Em Thu, Oct 22, 2015 at 11:22:40PM +0900, Namhyung Kim escreveu:
>> On Thu, Oct 22, 2015 at 11:13 PM, Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
>> > Em Thu, Oct 22, 2015 at 03:28:50PM +0900, Namhyung Kim escreveu:
>> >> +++ b/tools/perf/util/util.c
>> >> @@ -19,7 +19,7 @@
>> >>  struct callchain_param       callchain_param = {
>> >>       .mode   = CHAIN_GRAPH_ABS,
>> >> -     .order  = ORDER_CALLER,
>> >> +     .order  = ORDER_CALLEE,
>
>> > So, this isn't a revert of the previous default change, i.e. previously
>> > we used CHAIN_GRAPH_REL, should we keep CHAIN_GRAPH_ABS + callee?
>
>> Yes, it's not a revert.  I intentionally didn't change the print type.
>
> Ok, its just that I don't recall seeing the part of the discussion about
> keeping the change from REL to ABS.
>
>> > Also you forgot to fix the docs to mention this new default, I did it
>> > and the resulting patch, still with GRAPH_ABS follows:
>
>> This is not simple.  As Brendan said, --children is default on, so
>> users will see 'caller' ordering that's why I didn't change the doc.
>
> Ok, but the default as it stands after applying this patch is "graph,
> calee", so the docs should be changed to reflect that, yes, its not just
> that, we need to tell, in the --children doc, that it defaults to
> "caller".
>
> Will we also flip the default to --no-children? I would advocate that,
> together with showing a info box telling the user about this change and
> how to ask for it, including instructions on how to do that via
> ~/.perfconfig.

Not sure.  It seems too late to do it. ;-)

>
>> But I should mention it'll use 'callee' ordering when --no-chlidren.
>> I'm about to send doc fix patch Ingo requested, so please leave this
>> patch as is.
>
> Ok, its just that I thought you was already asleep and was wanting to
> make progress on this 8-)

Yeah, it's late.  I'll go to bed soon.. :)

>
> Will wait for your patches and instead try to fix the annotation bug
> that leads 'perf report --tui -S some_symbol_name' to exit without
> printing anything, that Ingo reported, only happens in --tui, because
> --stdio doesn't collects annotation info...

I guess -S option works only for symbols that have self overhead..

Thanks,
Namhyung

  reply	other threads:[~2015-10-22 15:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22  6:28 [PATCH 1/3] perf tools: Move callchain help messages to callchain.h Namhyung Kim
2015-10-22  6:28 ` [PATCH 2/3] perf top: Support call-graph display options also Namhyung Kim
2015-10-22  8:23   ` Ingo Molnar
2015-10-22 12:20     ` Namhyung Kim
2015-10-22 13:57       ` Taeung Song
2015-10-22 14:34         ` Namhyung Kim
2015-10-22 18:38   ` Arnaldo Carvalho de Melo
2015-10-23  8:31   ` [tip:perf/core] " tip-bot for Namhyung Kim
2015-10-22  6:28 ` [RFC/PATCH 3/3] perf tools: Defaults to 'caller' callchain order only if --children is enabled Namhyung Kim
2015-10-22  7:32   ` Ingo Molnar
2015-10-22  7:38     ` Namhyung Kim
2015-10-22  9:49       ` Brendan Gregg
2015-10-22 14:03         ` Arnaldo Carvalho de Melo
2015-11-02 23:59           ` Brendan Gregg
2015-10-22 12:21       ` Frederic Weisbecker
2015-10-22  7:45   ` [RFC/PATCH RESEND " Namhyung Kim
2015-10-22 18:38     ` Arnaldo Carvalho de Melo
2015-10-23  8:31     ` [tip:perf/core] " tip-bot for Namhyung Kim
2015-10-22 12:19   ` [RFC/PATCH 3/3] " Frederic Weisbecker
2015-10-22 14:13   ` Arnaldo Carvalho de Melo
2015-10-22 14:22     ` Namhyung Kim
2015-10-22 14:37       ` Arnaldo Carvalho de Melo
2015-10-22 15:51         ` Namhyung Kim [this message]
2015-10-22 16:21           ` Arnaldo Carvalho de Melo
2015-10-22  8:02 ` [PATCH 1/3] perf tools: Move callchain help messages to callchain.h Ingo Molnar
2015-10-22 12:13   ` Namhyung Kim
2015-10-22 14:17     ` Arnaldo Carvalho de Melo
2015-10-23  9:59     ` Ingo Molnar
2015-10-23 14:27       ` Arnaldo Carvalho de Melo
2015-10-23 16:40         ` Arnaldo Carvalho de Melo
2015-10-22 18:38 ` Arnaldo Carvalho de Melo
2015-10-23  8:30 ` [tip:perf/core] " 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=CAM9d7chC9FkdFYEDic8EU3QLEmrJsY2-vv9VTjSnS7FMmdqsUg@mail.gmail.com \
    --to=namhyung@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=bp@suse.de \
    --cc=brendan.d.gregg@gmail.com \
    --cc=chandlerc@gmail.com \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=wangnan0@huawei.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

all inboxes | Powered by JetHome®