From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ian Rogers <irogers@google.com>,
James Clark <james.clark@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Jiri Olsa <jolsa@kernel.org>,
"Liang, Kan" <kan.liang@linux.intel.com>,
Mark Rutland <mark.rutland@arm.com>,
Will Deacon <will@kernel.org>,
Mike Leach <mike.leach@linaro.org>,
Graham Woodward <graham.woodward@arm.com>,
Paschalis.Mpeis@arm.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Leo Yan <leo.yan@arm.com>
Subject: Re: [PATCH v4 00/12] perf script: Refactor branch flags for Arm SPE
Date: Wed, 05 Mar 2025 09:14:38 -0800 [thread overview]
Message-ID: <174119487820.3243158.8048766791168980891.b4-ty@kernel.org> (raw)
In-Reply-To: <20250304111240.3378214-1-leo.yan@arm.com>
On Tue, 04 Mar 2025 11:12:28 +0000, Leo Yan wrote:
> This patch series refactors branch flags for support Arm SPE. The patch
> set is divided into two parts, the first part is for refactoring common
> code and the second part is for enabling Arm SPE.
>
> For refactoring branch flags, the sample flaghs are classified as branch
> types and events. A program branch type can be conditional branch,
> function call, return or expection taken. A branch event happens when
> taking a branch. This series combines branch types and the associated
> events to present a sample flag.
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
prev parent reply other threads:[~2025-03-05 17:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 11:12 Leo Yan
2025-03-04 11:12 ` [PATCH v4 01/12] perf script: Make printing flags reliable Leo Yan
2025-03-04 15:21 ` Adrian Hunter
2025-03-04 11:12 ` [PATCH v4 02/12] perf script: Refactor sample_flags_to_name() function Leo Yan
2025-03-04 11:12 ` [PATCH v4 03/12] perf script: Separate events from branch types Leo Yan
2025-03-04 11:12 ` [PATCH v4 04/12] perf script: Add not taken event for branches Leo Yan
2025-03-04 11:12 ` [PATCH v4 05/12] perf script: Add not taken event for branch stack Leo Yan
2025-03-04 11:12 ` [PATCH v4 06/12] perf arm-spe: Fix load-store operation checking Leo Yan
2025-03-04 11:12 ` [PATCH v4 07/12] perf arm-spe: Extend branch operations Leo Yan
2025-03-04 11:12 ` [PATCH v4 08/12] perf arm-spe: Decode transactional event Leo Yan
2025-03-04 11:12 ` [PATCH v4 09/12] perf arm-spe: Fill branch operations and events to record Leo Yan
2025-03-04 11:12 ` [PATCH v4 10/12] perf arm-spe: Set sample flags with supplement info Leo Yan
2025-03-04 11:12 ` [PATCH v4 11/12] perf arm-spe: Add branch stack Leo Yan
2025-03-04 11:12 ` [PATCH v4 12/12] perf arm-spe: Support previous branch target (PBT) address Leo Yan
2025-03-05 17:14 ` Namhyung Kim [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=174119487820.3243158.8048766791168980891.b4-ty@kernel.org \
--to=namhyung@kernel.org \
--cc=Paschalis.Mpeis@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=graham.woodward@arm.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=will@kernel.org \
/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®