From: Namhyung Kim <namhyung@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>, Kan Liang <kan.liang@intel.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Andi Kleen <andi@firstfloor.org>, Wang Nan <wangnan0@huawei.com>
Subject: Re: [PATCH 1/3] perf top: Fix freeze on --call-graph flat/folded
Date: Thu, 26 Nov 2015 22:52:56 +0900 [thread overview]
Message-ID: <20151126135256.GA18551@danjae.kornet> (raw)
In-Reply-To: <20151126083853.GA8822@krava.brq.redhat.com>
Hi Jiri,
On Thu, Nov 26, 2015 at 09:38:53AM +0100, Jiri Olsa wrote:
> On Thu, Nov 26, 2015 at 04:08:18PM +0900, Namhyung Kim wrote:
> > The callchain rbtree is rebuilt periodically, so it needs to
> > reinitialize the root everytime. Otherwise it can be stuck in the
> > rbtree insertion with stale pointers.
> >
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> > ---
> > tools/perf/util/callchain.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/tools/perf/util/callchain.c b/tools/perf/util/callchain.c
> > index fc3b1e0d09ee..564377d2bebf 100644
> > --- a/tools/perf/util/callchain.c
> > +++ b/tools/perf/util/callchain.c
> > @@ -290,6 +290,7 @@ static void
> > sort_chain_flat(struct rb_root *rb_root, struct callchain_root *root,
> > u64 min_hit, struct callchain_param *param __maybe_unused)
> > {
> > + *rb_root = RB_ROOT;
>
> it seems ok, but I did not find how this could be called twice?
>
> the only sort I can see is done within:
> __hists__insert_output_entry
>
> do we allow resorting of the callchains?
No, but I think it's possible though.
It's called from perf top's display thread.
display_thread()
-> while (!done)
-> perf_top__print_sym_table()
-> hists__output_resort()
-> __hists__insert_output_entry()
Thanks,
Namhyung
next prev parent reply other threads:[~2015-11-26 13:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 7:08 [PATCH 1/3] perf top: Fix freeze on --call-graph flat/folded Namhyung Kim
2015-11-26 7:08 ` [PATCH 2/3] perf callchain: Stop resolving callchains after invalid address Namhyung Kim
2015-11-26 7:43 ` Ingo Molnar
2015-11-26 14:12 ` Namhyung Kim
2015-11-27 7:48 ` Ingo Molnar
2015-11-26 13:14 ` David Ahern
2015-11-26 15:00 ` Namhyung Kim
2015-11-26 15:48 ` David Ahern
2015-11-26 15:58 ` Jiri Olsa
2015-11-26 16:19 ` Arnaldo Carvalho de Melo
2015-12-02 5:20 ` Namhyung Kim
2015-11-26 7:08 ` [PATCH 3/3] perf callchain: Honor hide_unresolved Namhyung Kim
2015-11-26 8:46 ` Jiri Olsa
2015-11-26 16:20 ` Arnaldo Carvalho de Melo
2015-11-27 7:43 ` [tip:perf/core] " tip-bot for Namhyung Kim
2015-11-26 8:38 ` [PATCH 1/3] perf top: Fix freeze on --call-graph flat/folded Jiri Olsa
2015-11-26 13:52 ` Namhyung Kim [this message]
2015-11-26 14:00 ` Jiri Olsa
2015-11-26 15:10 ` Namhyung Kim
2015-11-26 15:22 ` Jiri Olsa
2015-11-26 16:32 ` Arnaldo Carvalho de Melo
2015-11-27 7:43 ` [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=20151126135256.GA18551@danjae.kornet \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.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