From: Leo Yan <leo.yan@arm.com>
To: Yujie Liu <yujie.liu@intel.com>
Cc: linux-perf-users@vger.kernel.org, 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>,
"Liang, Kan" <kan.liang@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
Martin Liska <martin.liska@hey.com>,
James Clark <james.clark@linaro.org>,
Sandipan Das <sandipan.das@amd.com>
Subject: Re: [PATCH v2] perf script: Update brstack syntax documentation
Date: Wed, 12 Mar 2025 09:56:13 +0000 [thread overview]
Message-ID: <20250312095613.GL9682@e132581.arm.com> (raw)
In-Reply-To: <20250312072329.419020-1-yujie.liu@intel.com>
On Wed, Mar 12, 2025 at 03:23:29PM +0800, Yujie Liu wrote:
> The following commits added new fields/flags to the branch stack field
> list:
>
> commit 1f48989cdc7d ("perf script: Output branch sample type")
> commit 6ade6c646035 ("perf script: Show branch speculation info")
> commit 1e66dcff7b9b ("perf script: Add not taken event for branch stack")
>
> Update brstack syntax documentation to be consistent with the latest
> branch stack field list. Improve the descriptions to help users
> interpret the fields accurately.
>
> Signed-off-by: Yujie Liu <yujie.liu@intel.com>
Reviewed-by: Leo Yan <leo.yan@arm.com>
> ---
> Changes in v2:
> - Add not taken event (Namhyung, Leo)
> - Change field name from PRED to EVENT for generic use and furture
> extension (Leo)
>
> v1: https://lore.kernel.org/all/20250225061736.1698175-1-yujie.liu@intel.com/
> ---
> tools/perf/Documentation/perf-script.txt | 23 ++++++++++++++++-------
> 1 file changed, 16 insertions(+), 7 deletions(-)
>
> diff --git a/tools/perf/Documentation/perf-script.txt b/tools/perf/Documentation/perf-script.txt
> index b72866ef270b..28bec7e78bc8 100644
> --- a/tools/perf/Documentation/perf-script.txt
> +++ b/tools/perf/Documentation/perf-script.txt
> @@ -239,13 +239,22 @@ OPTIONS
> i.e., -F "" is not allowed.
>
> The brstack output includes branch related information with raw addresses using the
> - /v/v/v/v/cycles syntax in the following order:
> - FROM: branch source instruction
> - TO : branch target instruction
> - M/P/-: M=branch target mispredicted or branch direction was mispredicted, P=target predicted or direction predicted, -=not supported
> - X/- : X=branch inside a transactional region, -=not in transaction region or not supported
> - A/- : A=TSX abort entry, -=not aborted region or not supported
> - cycles
> + FROM/TO/EVENT/INTX/ABORT/CYCLES/TYPE/SPEC syntax in the following order:
> + FROM : branch source instruction
> + TO : branch target instruction
> + EVENT : M=branch target or direction was mispredicted
> + P=branch target or direction was predicted
> + N=branch not-taken
> + -=no event or not supported
> + INTX : X=branch inside a transactional region
> + -=branch not in transaction region or not supported
> + ABORT : A=TSX abort entry
> + -=not aborted region or not supported
> + CYCLES: the number of cycles that have elapsed since the last branch was recorded
> + TYPE : branch type: COND/UNCOND/IND/CALL/IND_CALL/RET etc.
> + -=not supported
> + SPEC : branch speculation info: SPEC_WRONG_PATH/NON_SPEC_CORRECT_PATH/SPEC_CORRECT_PATH
> + -=not supported
>
> The brstacksym is identical to brstack, except that the FROM and TO addresses are printed in a symbolic form if possible.
>
>
> base-commit: b10f74308e1305275e69ddde711ec817cc69e306
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-03-12 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 7:23 [PATCH v2] perf script: Update brstack syntax documentation Yujie Liu
2025-03-12 9:56 ` Leo Yan [this message]
2025-03-14 7:04 ` Sandipan Das
2025-03-14 17:43 ` 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=20250312095613.GL9682@e132581.arm.com \
--to=leo.yan@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.liska@hey.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=sandipan.das@amd.com \
--cc=yujie.liu@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;
as well as URLs for NNTP newsgroup(s).