public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 1/2 v2] perf script: Fix missing '+' indicator when branch counter reaches upper limit
Date: Thu, 30 Apr 2026 08:37:05 +0800	[thread overview]
Message-ID: <5c37bcc6-1c3d-43ba-b4e4-cce602ab55ce@linux.intel.com> (raw)
In-Reply-To: <20260429152917.178803-2-thomas.falcon@intel.com>


On 4/29/2026 11:29 PM, Thomas Falcon wrote:
> From: Dapeng Mi <dapeng1.mi@linux.intel.com>
>
> When displaying branch counter (br_cntr) information, a "+"
> suffix represents that event occurrences may have been lost
> due to branch counter saturation. However, this indicator was
> missing in perf script. Add it back.
>
> Before:
>
>  # Branch counter abbr list:
>  # cpu_core/event=0xc4,umask=0x20/ppp = A
>  # cpu_core/instructions/ = B
>  # cpu_core/MEM_INST_RETIRED.ALL_LOADS/ = C
>  # cpu_core/MEM_LOAD_RETIRED.L2_MISS/ = D
>  # '-' No event occurs
>  # '+' Event occurrences may be lost due to branch counter saturated
> ...
>         datasym+190:
>         00005567f9951676        jz 0x5567f995162dr_cntr: BBBC   # PRED 1 cycles [1]
> ...
> After:
> ...
>         datasym+190:
>         00005567f9951676        jz 0x5567f995162dr_cntr: BBB+C  # PRED 1 cycles [1]
> ...
>
> Signed-off-by: Dapeng Mi <dapeng1.mi@linux.intel.com>
> Signed-off-by: Thomas Falcon <thomas.falcon@intel.com>
> ---
>  tools/perf/builtin-script.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
> index c8ac9f01a36b..f865c8b2f95f 100644
> --- a/tools/perf/builtin-script.c
> +++ b/tools/perf/builtin-script.c
> @@ -1287,8 +1287,12 @@ static int ip__fprintf_jump(uint64_t ip, struct branch_entry *en,
>  			if (!verbose) {
>  				for (j = 0; j < num; j++)
>  					printed += fprintf(fp, "%s", pos->abbr_name);
> -			} else
> -				printed += fprintf(fp, "%s %d ", pos->name, num);
> +				if (num == mask)
> +					printed += fprintf(fp, "+");
> +			} else {
> +				printed += fprintf(fp, "%s %d%s", pos->name,
> +						   num, num == mask ? "+ " : " ");
> +			}
>  		}
>  		if (numprinted == 0 && !verbose)
>  			printed += fprintf(fp, "-");

Reviewed-by: Dapeng Mi <dapeng1.mi@linux.intel.com>



  reply	other threads:[~2026-04-30  0:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29 15:29 [PATCH 0/2 v2] perf: Fix missing branch counter information in script and annotate Thomas Falcon
2026-04-29 15:29 ` [PATCH 1/2 v2] perf script: Fix missing '+' indicator when branch counter reaches upper limit Thomas Falcon
2026-04-30  0:37   ` Mi, Dapeng [this message]
2026-04-29 15:29 ` [PATCH 2/2 v2] perf annotate: Fix missing branch counter column in TUI mode Thomas Falcon
2026-04-30  0:38   ` Mi, Dapeng

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=5c37bcc6-1c3d-43ba-b4e4-cce602ab55ce@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