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 v7] perf annotate: Fix sample events lost in stdio mode
Date: Fri, 26 Mar 2021 10:24:30 +0800 [thread overview]
Message-ID: <33ba152e-b8ef-3057-744a-51cb8c478ff2@huawei.com> (raw)
In-Reply-To: <20210319123527.173883-1-yangjihong1@huawei.com>
Hello,
ping :)
On 2021/3/19 20:35, Yang Jihong wrote:
> In hist__find_annotations function, since different hist_entry may point to 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 remove zfree in hists__find_annotations and
> change sort order to "dso,symbol" to avoid duplicate output when different
> processes correspond to the same symbol.
>
> Signed-off-by: Yang Jihong <yangjihong1@huawei.com>
> ---
>
> Changes since v6:
> - Remove separate setup_sorting() for branch mode.
>
> Changes since v5:
> - Add Signed-off-by tag.
>
> Changes since v4:
> - Use the same sort key "dso,symbol" in branch stack mode.
>
> Changes since v3:
> - Modify the first line of comments.
>
> Changes since v2:
> - Remove zfree in hists__find_annotations.
> - Change sort order to avoid duplicate output.
>
> Changes since v1:
> - Change processed flag variable from u8 to bool.
>
> tools/perf/builtin-annotate.c | 29 +++++++++++++++--------------
> 1 file changed, 15 insertions(+), 14 deletions(-)
>
> diff --git a/tools/perf/builtin-annotate.c b/tools/perf/builtin-annotate.c
> index a23ba6bb99b6..795c2ac7fcd1 100644
> --- a/tools/perf/builtin-annotate.c
> +++ b/tools/perf/builtin-annotate.c
> @@ -374,13 +374,6 @@ static void hists__find_annotations(struct hists *hists,
> } else {
> hist_entry__tty_annotate(he, evsel, ann);
> 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);
> }
> }
> }
> @@ -619,14 +612,22 @@ int cmd_annotate(int argc, const char **argv)
>
> setup_browser(true);
>
> - if ((use_browser == 1 || annotate.use_stdio2) && annotate.has_br_stack) {
> + /*
> + * Events of different processes may correspond to the same
> + * symbol, we do not care about the processes in annotate,
> + * set sort order to avoid repeated output.
> + */
> + sort_order = "dso,symbol";
> +
> + /*
> + * Set SORT_MODE__BRANCH so that annotate display IPC/Cycle
> + * if branch info is in perf data in TUI mode.
> + */
> + if ((use_browser == 1 || annotate.use_stdio2) && annotate.has_br_stack)
> sort__mode = SORT_MODE__BRANCH;
> - if (setup_sorting(annotate.session->evlist) < 0)
> - usage_with_options(annotate_usage, options);
> - } else {
> - if (setup_sorting(NULL) < 0)
> - usage_with_options(annotate_usage, options);
> - }
> +
> + if (setup_sorting(NULL) < 0)
> + usage_with_options(annotate_usage, options);
>
> ret = __cmd_annotate(&annotate);
>
>
next prev parent reply other threads:[~2021-03-26 2:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 12:35 Yang Jihong
2021-03-26 2:24 ` Yang Jihong [this message]
2021-03-26 3:25 ` Namhyung Kim
2021-03-26 12:06 ` Arnaldo Carvalho de Melo
2021-03-27 2:15 ` Yang Jihong
2021-03-30 7:26 ` Namhyung Kim
2021-03-31 2:18 ` Yang Jihong
2021-04-12 7:22 ` Yang Jihong
2021-04-14 12:23 ` Arnaldo Carvalho de Melo
2021-04-14 13:15 ` 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=33ba152e-b8ef-3057-744a-51cb8c478ff2@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®