From: Namhyung Kim <namhyung@kernel.org>
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>,
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>, Leo Yan <leo.yan@arm.com>
Subject: Re: [PATCH] perf script: Update brstack syntax documentation
Date: Mon, 10 Mar 2025 14:13:56 -0700 [thread overview]
Message-ID: <Z89WFKPIxWBgN6q2@google.com> (raw)
In-Reply-To: <Z8q51Mcz/9QenjnC@yujie-X299>
Hello,
On Fri, Mar 07, 2025 at 05:18:12PM +0800, Yujie Liu wrote:
> Hi, friendly ping on this perf script doc fix. Thanks.
Sorry for the late reply.
>
> On Tue, Feb 25, 2025 at 02:17:36PM +0800, Yujie Liu wrote:
> > The following commits appended new fields to the end of the branch info
> > list, such as branch type and branch speculation info.
> >
> > commit 1f48989cdc7d ("perf script: Output branch sample type")
> > commit 6ade6c646035 ("perf script: Show branch speculation info")
> >
> > Update brstack syntax documentation to be consistent with the latest
> > branch info list. Improve the descriptions to help users interpret the
> > fields accurately.
Thanks for your work, but can you please update it again with recent
changes from Leo?
https://lore.kernel.org/linux-perf-users/20250304111240.3378214-1-leo.yan@arm.com/
Thanks,
Namhyung
> >
> > Signed-off-by: Yujie Liu <yujie.liu@intel.com>
> > ---
> > tools/perf/Documentation/perf-script.txt | 16 +++++++++-------
> > 1 file changed, 9 insertions(+), 7 deletions(-)
> >
> > diff --git a/tools/perf/Documentation/perf-script.txt b/tools/perf/Documentation/perf-script.txt
> > index b72866ef270b..8bd105084280 100644
> > --- a/tools/perf/Documentation/perf-script.txt
> > +++ b/tools/perf/Documentation/perf-script.txt
> > @@ -239,13 +239,15 @@ 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/PRED/INTX/ABORT/CYCLES/TYPE/SPEC syntax in the following order:
> > + FROM : branch source instruction
> > + TO : branch target instruction
> > + PRED : M=branch target mispredicted or branch direction was mispredicted, P=target predicted or direction predicted, -=not supported
> > + INTX : X=branch inside a transactional region, -=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
> > + SPEC : branch speculation info
> >
> > The brstacksym is identical to brstack, except that the FROM and TO addresses are printed in a symbolic form if possible.
> >
> > --
> > 2.34.1
> >
next prev parent reply other threads:[~2025-03-10 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 6:17 [PATCH] perf script: Update brstack syntax documentation Yujie Liu
2025-03-07 9:18 ` Yujie Liu
2025-03-10 21:13 ` Namhyung Kim [this message]
2025-03-11 3:20 ` Yujie Liu
2025-03-11 8:14 ` Leo Yan
2025-03-11 9:04 ` Yujie Liu
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=Z89WFKPIxWBgN6q2@google.com \
--to=namhyung@kernel.org \
--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=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@arm.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=peterz@infradead.org \
--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