From: Yang Jihong <yangjihong1@huawei.com>
To: <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
<mark.rutland@arm.com>, <alexander.shishkin@linux.intel.com>,
<jolsa@redhat.com>, <namhyung@kernel.org>,
<yao.jin@linux.intel.com>, <gustavoars@kernel.org>,
<mliska@suse.cz>, <linux-kernel@vger.kernel.org>
Cc: <zhangjinhao2@huawei.com>
Subject: Re: [PATCH] perf annotate: Fix sample events lost in stdio mode
Date: Thu, 11 Mar 2021 16:48:18 +0800 [thread overview]
Message-ID: <53ff575f-1fcf-6650-76ad-a0304f6bdf15@huawei.com> (raw)
In-Reply-To: <20210306082859.179541-1-yangjihong1@huawei.com>
Hello,
On 2021/3/6 16:28, Yang Jihong wrote:
> In hist__find_annotations function, since have a hist_entry per IP for the same
> symbol, we free notes->src to signal already processed this symbol in stdio mode;
> when annotate, entry will skipped if notes->src is NULL to avoid repeated output.
>
> However, there is a problem, for example, run the following command:
>
> # perf record -e branch-misses -e branch-instructions -a sleep 1
>
> perf.data file contains different types of sample event.
>
> If the same IP sample event exists in branch-misses and branch-instructions,
> this event uses the same symbol. When annotate branch-misses events, notes->src
> corresponding to this event is set to null, as a result, when annotate
> branch-instructions events, this event is skipped and no annotate is output.
>
> Solution of this patch is to add a u8 member to struct sym_hist and use a bit to
> indicate whether the symbol has been processed.
> Because different types of event correspond to different sym_hist, no conflict
> occurs.
> ---
> tools/perf/builtin-annotate.c | 22 ++++++++++++++--------
> tools/perf/util/annotate.h | 4 ++++
> 2 files changed, 18 insertions(+), 8 deletions(-)
>
> diff --git a/tools/perf/builtin-annotate.c b/tools/perf/builtin-annotate.c
> index a23ba6bb99b6..c8c67892ae82 100644
> --- a/tools/perf/builtin-annotate.c
> +++ b/tools/perf/builtin-annotate.c
> @@ -372,15 +372,21 @@ static void hists__find_annotations(struct hists *hists,
> if (next != NULL)
> nd = next;
> } else {
> - hist_entry__tty_annotate(he, evsel, ann);
> + struct sym_hist *h = annotated_source__histogram(notes->src,
> + evsel->idx);
> +
> + if (h->processed == 0) {
> + hist_entry__tty_annotate(he, evsel, ann);
> +
> + /*
> + * Since we have a hist_entry per IP for the same
> + * symbol, set processed flag of evsel in sym_hist
> + * to signal we already processed this symbol.
> + */
> + h->processed = 1;
> + }
> +
> nd = rb_next(nd);
> - /*
> - * Since we have a hist_entry per IP for the same
> - * symbol, free he->ms.sym->src to signal we already
> - * processed this symbol.
> - */
> - zfree(¬es->src->cycles_hist);
> - zfree(¬es->src);
> }
> }
> }
> diff --git a/tools/perf/util/annotate.h b/tools/perf/util/annotate.h
> index 096cdaf21b01..89872bfdc958 100644
> --- a/tools/perf/util/annotate.h
> +++ b/tools/perf/util/annotate.h
> @@ -228,6 +228,10 @@ void symbol__calc_percent(struct symbol *sym, struct evsel *evsel);
> struct sym_hist {
> u64 nr_samples;
> u64 period;
> +
> + u8 processed : 1, /* whether symbol has been processed, used for annotate */
> + __reserved : 7;
> +
> struct sym_hist_entry addr[];
> };
>
>
Please check whether this solution is feasible, look forward to your review.
Thanks,
Yang
next prev parent reply other threads:[~2021-03-11 8:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 8:28 Yang Jihong
2021-03-11 8:48 ` Yang Jihong [this message]
2021-03-11 14:42 ` Namhyung Kim
2021-03-12 3:24 ` Yang Jihong
2021-03-12 5:49 ` Namhyung Kim
2021-03-12 7:18 ` Yang Jihong
2021-03-12 8:39 ` Namhyung Kim
2021-03-12 10:20 ` Yang Jihong
2021-03-13 2:00 ` Yang Jihong
2021-03-13 2:23 ` Yang Jihong
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=53ff575f-1fcf-6650-76ad-a0304f6bdf15@huawei.com \
--to=yangjihong1@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=gustavoars@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mliska@suse.cz \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=yao.jin@linux.intel.com \
--cc=zhangjinhao2@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®