From: Anshuman Khandual <anshuman.khandual@arm.com>
To: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, peterz@infradead.org,
acme@kernel.org, mark.rutland@arm.com, will@kernel.org
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
James Clark <james.clark@arm.com>, Rob Herring <robh@kernel.org>,
Marc Zyngier <maz@kernel.org>, Ingo Molnar <mingo@redhat.com>,
linux-perf-users@vger.kernel.org
Subject: [PATCH 4/8] arm64/perf: Update struct pmu_hw_events for BRBE
Date: Mon, 13 Jun 2022 15:31:15 +0530 [thread overview]
Message-ID: <20220613100119.684673-5-anshuman.khandual@arm.com> (raw)
In-Reply-To: <20220613100119.684673-1-anshuman.khandual@arm.com>
A single perf event instance BRBE related contexts and data will be tracked
in struct pmu_hw_events. Hence update the structure to accommodate required
details related to BRBE.
Cc: Will Deacon <will@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
---
include/linux/perf/arm_pmu.h | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/include/linux/perf/arm_pmu.h b/include/linux/perf/arm_pmu.h
index 3d427ac0ca45..18e519e4e658 100644
--- a/include/linux/perf/arm_pmu.h
+++ b/include/linux/perf/arm_pmu.h
@@ -43,6 +43,11 @@
}, \
}
+/*
+ * Maximum branch records in BRBE
+ */
+#define BRBE_MAX_ENTRIES 64
+
/* The events for a given PMU register set. */
struct pmu_hw_events {
/*
@@ -69,6 +74,23 @@ struct pmu_hw_events {
struct arm_pmu *percpu_pmu;
int irq;
+
+ /* Detected BRBE attributes */
+ bool v1p1;
+ int brbe_cc;
+ int brbe_nr;
+
+ /* Evaluated BRBE configuration */
+ u64 brbfcr;
+ u64 brbcr;
+
+ /* Tracked BRBE context */
+ unsigned int brbe_users;
+ void *brbe_context;
+
+ /* Captured BRBE buffer - copied as is into perf_sample_data */
+ struct perf_branch_stack brbe_stack;
+ struct perf_branch_entry brbe_entries[BRBE_MAX_ENTRIES];
};
enum armpmu_attr_groups {
--
2.25.1
next prev parent reply other threads:[~2022-06-13 10:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 10:01 [PATCH 0/8] arm64/perf: Enable branch stack sampling Anshuman Khandual
2022-06-13 10:01 ` [PATCH 1/8] perf: Consolidate branch sample filter helpers Anshuman Khandual
2022-06-13 20:32 ` kernel test robot
2022-06-14 1:36 ` Anshuman Khandual
2022-06-14 11:13 ` [kbuild-all] " Chen, Rong A
2022-06-13 10:01 ` [PATCH 2/8] arm64/perf: Add register definitions for BRBE Anshuman Khandual
2022-06-13 10:01 ` [PATCH 3/8] arm64/perf: Update struct arm_pmu " Anshuman Khandual
2022-06-13 10:01 ` Anshuman Khandual [this message]
2022-06-13 10:01 ` [PATCH 5/8] driver/perf/arm_pmu_platform: Add support for BRBE attributes detection Anshuman Khandual
2022-06-13 10:01 ` [PATCH 6/8] arm64/perf: Drive BRBE from perf event states Anshuman Khandual
2022-06-13 10:01 ` [PATCH 7/8] arm64/perf: Add BRBE driver Anshuman Khandual
2022-06-13 12:16 ` German Gomez
2022-06-14 1:44 ` Anshuman Khandual
2022-06-13 10:01 ` [PATCH 8/8] arm64/perf: Enable branch stack sampling Anshuman Khandual
2022-06-27 11:01 ` [PATCH 0/8] " Will Deacon
2022-06-28 7:40 ` Anshuman Khandual
2022-07-05 12:09 ` Will Deacon
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=20220613100119.684673-5-anshuman.khandual@arm.com \
--to=anshuman.khandual@arm.com \
--cc=acme@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.clark@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=maz@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).