From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Brendan Gregg <brendan.d.gregg@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Borislav Petkov <bp@suse.de>,
Chandler Carruth <chandlerc@gmail.com>,
David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Stephane Eranian <eranian@google.com>,
Wang Nan <wangnan0@huawei.com>
Subject: Re: [PATCH 13/16] perf callchain: Switch default to 'graph,0.5,caller'
Date: Wed, 21 Oct 2015 10:21:22 -0300 [thread overview]
Message-ID: <20151021132122.GD10639@kernel.org> (raw)
In-Reply-To: <20151021080645.GA9318@gmail.com>
Em Wed, Oct 21, 2015 at 10:06:45AM +0200, Ingo Molnar escreveu:
> * Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com> wrote:
> > Indeed, finding a default that is deemed adequate for most people is, ho-hum,
> > difficult 8-)
> > Ingo, what do you think?
> So I think the new default is a lot more intuitive, because it starts with a high
> level top-down 'overview' kind of output, allowing one to drill down to the
> details.
> That's what most other tools do as well by default, and people migrating to perf
> found it pretty confusing that we do a bottom-up kind of callgraph.
> To people using perf for the first time it does not matter nearly as much, but
> intuitiveness is still a factor.
> The new default requires good call-chains and good symbol resolution to be
> maximally effective, but we want perfect callchains and symbols in any case,
> right?
Sure, but in hindsight, we could've fixed those problems before flipping
the switch :-)
And also we didn't care about it that much because for callee based
callchains they are far from the focus point.
- Arnaldo
next prev parent reply other threads:[~2015-10-21 13:21 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 21:03 [GIT PULL 00/16] perf/core improvements and fixes Arnaldo Carvalho de Melo
2015-10-05 21:03 ` [PATCH 01/16] tools lib api fs: No need to use PATH_MAX + 1 Arnaldo Carvalho de Melo
2015-10-05 21:03 ` [PATCH 02/16] perf evlist: Display DATA_SRC sample type bit Arnaldo Carvalho de Melo
2015-10-05 21:03 ` [PATCH 03/16] perf annotate: Fix sizeof_sym_hist overflow issue Arnaldo Carvalho de Melo
2015-10-05 21:03 ` [PATCH 04/16] perf tools: Export perf_event_attr__set_max_precise_ip() Arnaldo Carvalho de Melo
2015-10-05 21:03 ` [PATCH 05/16] perf tools: Introduce 'P' modifier to request max precision Arnaldo Carvalho de Melo
2015-10-05 21:03 ` [PATCH 06/16] perf tests: Add parsing test for 'P' modifier Arnaldo Carvalho de Melo
2015-10-05 21:03 ` [PATCH 07/16] perf tools: Add support for sorting on the iaddr Arnaldo Carvalho de Melo
2015-10-05 21:03 ` [PATCH 08/16] perf tools: Setup proper width for symbol_iaddr field Arnaldo Carvalho de Melo
2015-10-05 21:03 ` [PATCH 09/16] perf tools: Handle -h and -v options Arnaldo Carvalho de Melo
2015-10-05 21:03 ` [PATCH 10/16] perf tests: Add arch tests Arnaldo Carvalho de Melo
2015-10-05 21:03 ` [PATCH 11/16] perf tests: Move x86 tests into arch directory Arnaldo Carvalho de Melo
2015-10-05 21:03 ` [PATCH 12/16] perf tests: Add Intel CQM test Arnaldo Carvalho de Melo
2015-10-05 21:03 ` [PATCH 13/16] perf callchain: Switch default to 'graph,0.5,caller' Arnaldo Carvalho de Melo
2015-10-09 20:34 ` Brendan Gregg
2015-10-09 21:56 ` Arnaldo Carvalho de Melo
2015-10-09 22:10 ` Brendan Gregg
2015-10-09 22:25 ` Arnaldo Carvalho de Melo
2015-10-20 0:16 ` Brendan Gregg
2015-10-20 12:00 ` Arnaldo Carvalho de Melo
2015-10-20 12:19 ` Frederic Weisbecker
2015-10-20 13:06 ` Arnaldo Carvalho de Melo
2015-10-20 17:21 ` Frederic Weisbecker
2015-10-20 18:44 ` Arnaldo Carvalho de Melo
2015-10-21 1:21 ` Namhyung Kim
2015-10-21 13:24 ` Arnaldo Carvalho de Melo
2015-10-21 8:09 ` Namhyung Kim
2015-10-21 11:57 ` Wangnan (F)
2015-10-21 16:35 ` Frederic Weisbecker
[not found] ` <CAAwGriEtYeBytGt9x24=uUqSEy5oJ2HigfA2KXnKyrAioKrtNg@mail.gmail.com>
2015-10-21 16:27 ` Frederic Weisbecker
2015-10-21 18:28 ` Brendan Gregg
2015-10-21 19:23 ` Arnaldo Carvalho de Melo
2015-10-22 0:44 ` Brendan Gregg
2015-10-21 8:06 ` Ingo Molnar
2015-10-21 13:21 ` Arnaldo Carvalho de Melo [this message]
2015-10-21 19:18 ` Brendan Gregg
2015-10-10 7:09 ` Ingo Molnar
2015-10-10 7:34 ` Brendan Gregg
2015-10-10 9:07 ` Ingo Molnar
2015-10-12 15:27 ` Frederic Weisbecker
2015-10-13 4:26 ` Namhyung Kim
2015-10-19 23:50 ` Brendan Gregg
2015-10-21 7:29 ` Namhyung Kim
2015-10-20 13:23 ` Wangnan (F)
2015-10-20 13:38 ` Arnaldo Carvalho de Melo
2015-10-21 1:44 ` Namhyung Kim
2015-10-21 8:48 ` Ingo Molnar
2015-10-21 13:43 ` Arnaldo Carvalho de Melo
2015-10-21 13:46 ` Arnaldo Carvalho de Melo
2015-10-22 8:46 ` Ingo Molnar
2015-10-22 12:36 ` Namhyung Kim
2015-10-05 21:03 ` [PATCH 14/16] perf ui browser: Optional horizontal scrolling key binding Arnaldo Carvalho de Melo
2015-10-05 21:03 ` [PATCH 15/16] perf hists browser: Implement horizontal scrolling Arnaldo Carvalho de Melo
2015-10-05 21:03 ` [PATCH 16/16] perf tools: Fail properly in case pattern matching fails to find tracepoint Arnaldo Carvalho de Melo
2015-10-06 7:09 ` [GIT PULL 00/16] perf/core improvements and fixes Ingo Molnar
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=20151021132122.GD10639@kernel.org \
--to=arnaldo.melo@gmail.com \
--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=namhyung@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;
as well as URLs for NNTP newsgroup(s).