From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH 2/2] perf top: Fix event group with more than two events
Date: Wed, 28 Aug 2019 11:36:44 -0300 [thread overview]
Message-ID: <20190828143644.GC5632@kernel.org> (raw)
In-Reply-To: <20190827231555.121411-2-namhyung@kernel.org>
Em Wed, Aug 28, 2019 at 08:15:55AM +0900, Namhyung Kim escreveu:
> The event group feature links relevant hist entries among events so
> that they can be displayed together. During the link process, each
> hist entry in non-leader events is connected to a hist entry in the
> leader event. This is done in order of events specified in the
> command line so it assumes that events are linked in the order.
>
> But perf top can break the assumption since it does the link process
> multiple times. For example, a hist entry can be in the third event
> only at first so it's linked after the leader. Some time later,
> second event has a hist entry for it and it'll be linked after the
> entry of the third event.
>
> This makes the code compilicated to deal with such unordered entries.
> This patch simply unlink all the entries after it's printed so that
> they can assume the correct order after the repeated link process.
> Also it'd be easy to deal with decaying old entries IMHO.
Excellent, I just tested it with:
# perf top --show-total-period -e '{cycles,instructions,cache-references,cache-misses}'
And the total period goes down for all evsels when that symbol is
quiescent between screen refreshes, and no crash, all seems to be
working as expected, thanks for fixing this!
Also when pressing 'A' the annotation also seems to be working.
All applied.
- Arnaldo
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
> tools/perf/builtin-top.c | 6 ++++++
> tools/perf/util/hist.c | 39 +++++++++++++++++++++------------------
> tools/perf/util/hist.h | 1 +
> 3 files changed, 28 insertions(+), 18 deletions(-)
>
> diff --git a/tools/perf/builtin-top.c b/tools/perf/builtin-top.c
> index 9d3059d2029d..b871dd72e4bd 100644
> --- a/tools/perf/builtin-top.c
> +++ b/tools/perf/builtin-top.c
> @@ -272,6 +272,12 @@ static void evlist__resort_hists(struct perf_top *t)
> evlist__for_each_entry(evlist, pos) {
> struct hists *hists = evsel__hists(pos);
>
> + /*
> + * unlink existing entries so that they can be linked
> + * in a correct order in hists__match() below.
> + */
> + hists__unlink(hists);
> +
> if (evlist->enabled) {
> if (t->zero) {
> hists__delete_entries(hists);
> diff --git a/tools/perf/util/hist.c b/tools/perf/util/hist.c
> index 8efbf58dc3d0..47401210e087 100644
> --- a/tools/perf/util/hist.c
> +++ b/tools/perf/util/hist.c
> @@ -2436,7 +2436,7 @@ void hists__match(struct hists *leader, struct hists *other)
> {
> struct rb_root_cached *root;
> struct rb_node *nd;
> - struct hist_entry *pos, *pair, *pos_pair, *tmp_pair;
> + struct hist_entry *pos, *pair;
>
> if (symbol_conf.report_hierarchy) {
> /* hierarchy report always collapses entries */
> @@ -2453,24 +2453,8 @@ void hists__match(struct hists *leader, struct hists *other)
> pos = rb_entry(nd, struct hist_entry, rb_node_in);
> pair = hists__find_entry(other, pos);
>
> - if (pair && list_empty(&pair->pairs.node)) {
> - list_for_each_entry_safe(pos_pair, tmp_pair, &pos->pairs.head, pairs.node) {
> - if (pos_pair->hists == other) {
> - /*
> - * XXX maybe decayed entries can appear
> - * here? but then we would have use
> - * after free, as decayed entries are
> - * freed see hists__delete_entry
> - */
> - BUG_ON(!pos_pair->dummy);
> - list_del_init(&pos_pair->pairs.node);
> - hist_entry__delete(pos_pair);
> - break;
> - }
> - }
> -
> + if (pair)
> hist_entry__add_pair(pair, pos);
> - }
> }
> }
>
> @@ -2555,6 +2539,25 @@ int hists__link(struct hists *leader, struct hists *other)
> return 0;
> }
>
> +int hists__unlink(struct hists *hists)
> +{
> + struct rb_root_cached *root;
> + struct rb_node *nd;
> + struct hist_entry *pos;
> +
> + if (hists__has(hists, need_collapse))
> + root = &hists->entries_collapsed;
> + else
> + root = hists->entries_in;
> +
> + for (nd = rb_first_cached(root); nd; nd = rb_next(nd)) {
> + pos = rb_entry(nd, struct hist_entry, rb_node_in);
> + list_del_init(&pos->pairs.node);
> + }
> +
> + return 0;
> +}
> +
> void hist__account_cycles(struct branch_stack *bs, struct addr_location *al,
> struct perf_sample *sample, bool nonany_branch_mode)
> {
> diff --git a/tools/perf/util/hist.h b/tools/perf/util/hist.h
> index 83d5fc15429c..7b9267ebebeb 100644
> --- a/tools/perf/util/hist.h
> +++ b/tools/perf/util/hist.h
> @@ -217,6 +217,7 @@ void hists__calc_col_len(struct hists *hists, struct hist_entry *he);
>
> void hists__match(struct hists *leader, struct hists *other);
> int hists__link(struct hists *leader, struct hists *other);
> +int hists__unlink(struct hists *hists);
>
> struct hists_evsel {
> struct evsel evsel;
> --
> 2.23.0.187.g17f5b7556c-goog
--
- Arnaldo
next prev parent reply other threads:[~2019-08-28 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 23:15 [PATCH 1/2] perf top: Decay all events in the evlist Namhyung Kim
2019-08-27 23:15 ` [PATCH 2/2] perf top: Fix event group with more than two events Namhyung Kim
2019-08-28 14:36 ` Arnaldo Carvalho de Melo [this message]
2019-08-29 19:01 ` [tip: perf/core] " tip-bot2 for Namhyung Kim
2019-08-28 12:49 ` [PATCH 1/2] perf top: Decay all events in the evlist Arnaldo Carvalho de Melo
2019-08-30 3:58 ` Namhyung Kim
2019-08-29 19:01 ` [tip: perf/core] " tip-bot2 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=20190828143644.GC5632@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.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.