From: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
To: Thomas Falcon <thomas.falcon@intel.com>,
linux-perf-users@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>
Subject: Re: [PATCH 2/2] perf/annotate: Fix missing branch counter column in TUI mode
Date: Wed, 15 Apr 2026 10:30:26 +0800 [thread overview]
Message-ID: <4a8a58c2-36d3-483a-bca0-5c414d4bf7ab@linux.intel.com> (raw)
In-Reply-To: <20260410194000.219846-2-thomas.falcon@intel.com>
On 4/11/2026 3:40 AM, Thomas Falcon wrote:
> perf annotate checks that evlist->nr_br_cntr has been incremented
> to determine whether to show branch counter information. However,
> this data is not populated until after the check when events are
> processed. Therefore, this counter will always be less than zero
> and the Branch Count column is never shown. Do this check after
> events have been processed and branch counter data is updated.
>
> Signed-off-by: Thomas Falcon <thomas.falcon@intel.com>
> ---
> tools/perf/builtin-annotate.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/builtin-annotate.c b/tools/perf/builtin-annotate.c
> index 5e57b78548f4..7fe23b05306f 100644
> --- a/tools/perf/builtin-annotate.c
> +++ b/tools/perf/builtin-annotate.c
> @@ -563,6 +563,9 @@ static int __cmd_annotate(struct perf_annotate *ann)
> if (ret)
> goto out;
>
> + if (session->evlist->nr_br_cntr > 0)
Do we need to check if annotate.has_br_stack is true before setting
show_br_cntr to true? Thanks.
> + annotate_opts.show_br_cntr = true;
> +
> if (dump_trace) {
> perf_session__fprintf_nr_events(session, stdout);
> evlist__fprintf_nr_events(session->evlist, stdout);
> @@ -928,8 +931,6 @@ int cmd_annotate(int argc, const char **argv)
> */
> if ((use_browser == 1 || annotate.use_stdio2) && annotate.has_br_stack) {
> sort__mode = SORT_MODE__BRANCH;
> - if (annotate.session->evlist->nr_br_cntr > 0)
> - annotate_opts.show_br_cntr = true;
> }
>
> if (setup_sorting(/*evlist=*/NULL, perf_session__env(annotate.session)) < 0)
prev parent reply other threads:[~2026-04-15 2:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 19:39 [PATCH 1/2] perf script: Add missed "+" if br_cntr reaches upper limit Thomas Falcon
2026-04-10 19:40 ` [PATCH 2/2] perf/annotate: Fix missing branch counter column in TUI mode Thomas Falcon
2026-04-10 20:01 ` sashiko-bot
2026-04-10 20:05 ` Falcon, Thomas
2026-04-10 20:19 ` [PATCH v2 " Thomas Falcon
2026-04-15 2:30 ` Mi, Dapeng [this message]
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=4a8a58c2-36d3-483a-bca0-5c414d4bf7ab@linux.intel.com \
--to=dapeng1.mi@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=thomas.falcon@intel.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