From: German Gomez <german.gomez@arm.com>
To: linux-eng@arm.com
Cc: james.clark@arm.com, German Gomez <german.gomez@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] perf: arm_spe: make the PMSCR CX bit[3] consistent across the session
Date: Thu, 13 Jan 2022 17:54:16 +0000 [thread overview]
Message-ID: <20220113175417.5523-2-german.gomez@arm.com> (raw)
In-Reply-To: <20220113175417.5523-1-german.gomez@arm.com>
The ARM SPE driver will seenablet the CX bit in the PMSCR register if it
detects that the profiler (perf tool) has enough capabilities during the
initialization of the PMU event in the "arm_spe_pmu_event_init" callback:
reg = arm_spe_event_to_pmscr(event);
if (!perfmon_capable() &&
(reg & (BIT(SYS_PMSCR_EL1_PA_SHIFT) |
BIT(SYS_PMSCR_EL1_CX_SHIFT) |
BIT(SYS_PMSCR_EL1_PCT_SHIFT))))
return -EACCES;
This implies that the CX bit should remain consistent across the entire
duration of the session. However, the value of the bit is later being
changed (from 0 to 1 and vice versa) in the "arm_spe_pmu_start" callback
Consider this example:
1. Run a process in the background with privileges in CPU0
$ taskset --cpu-list 0 sudo dd if=/dev/random of=/dev/null &
[3] 3806
2. Begin a perf session without privileges (we shouldn't see CONTEXT packets)
$ perf record -e arm_spe_0// -C0 -- sleep 1
$ perf report -D | grep CONTEXT
. 0000000e: 65 df 0e 00 00 CONTEXT 0xedf el2
. 0000004e: 65 df 0e 00 00 CONTEXT 0xedf el2
. 0000008e: 65 df 0e 00 00 CONTEXT 0xedf el2
[...]
One way to fix this is by caching the value of the CX bit during the
initialization of the PMU event, so that it remains consistent during
the session.
Signed-off-by: German Gomez <german.gomez@arm.com>
---
drivers/perf/arm_spe_pmu.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/perf/arm_spe_pmu.c b/drivers/perf/arm_spe_pmu.c
index d44bcc29d..8515bf85c 100644
--- a/drivers/perf/arm_spe_pmu.c
+++ b/drivers/perf/arm_spe_pmu.c
@@ -57,6 +57,7 @@ struct arm_spe_pmu {
u16 pmsver;
u16 min_period;
u16 counter_sz;
+ bool pmscr_cx;
#define SPE_PMU_FEAT_FILT_EVT (1UL << 0)
#define SPE_PMU_FEAT_FILT_TYP (1UL << 1)
@@ -260,6 +261,7 @@ static const struct attribute_group *arm_spe_pmu_attr_groups[] = {
static u64 arm_spe_event_to_pmscr(struct perf_event *event)
{
struct perf_event_attr *attr = &event->attr;
+ struct arm_spe_pmu *spe_pmu = to_spe_pmu(event->pmu);
u64 reg = 0;
reg |= ATTR_CFG_GET_FLD(attr, ts_enable) << SYS_PMSCR_EL1_TS_SHIFT;
@@ -272,7 +274,7 @@ static u64 arm_spe_event_to_pmscr(struct perf_event *event)
if (!attr->exclude_kernel)
reg |= BIT(SYS_PMSCR_EL1_E1SPE_SHIFT);
- if (IS_ENABLED(CONFIG_PID_IN_CONTEXTIDR) && perfmon_capable())
+ if (IS_ENABLED(CONFIG_PID_IN_CONTEXTIDR) && spe_pmu->pmscr_cx)
reg |= BIT(SYS_PMSCR_EL1_CX_SHIFT);
return reg;
@@ -709,10 +711,10 @@ static int arm_spe_pmu_event_init(struct perf_event *event)
!(spe_pmu->features & SPE_PMU_FEAT_FILT_LAT))
return -EOPNOTSUPP;
+ spe_pmu->pmscr_cx = perfmon_capable();
reg = arm_spe_event_to_pmscr(event);
if (!perfmon_capable() &&
(reg & (BIT(SYS_PMSCR_EL1_PA_SHIFT) |
- BIT(SYS_PMSCR_EL1_CX_SHIFT) |
BIT(SYS_PMSCR_EL1_PCT_SHIFT))))
return -EACCES;
--
2.25.1
next prev parent reply other threads:[~2022-01-13 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 17:54 [PATCH 0/2] " German Gomez
2022-01-13 17:54 ` German Gomez [this message]
2022-01-13 17:54 ` [PATCH 2/2] perf: arm_spe: Enable CONTEXT packets if profiling in CPU mode German Gomez
2022-01-14 9:31 ` [PATCH 0/2] perf: arm_spe: make the PMSCR CX bit[3] consistent across the session German Gomez
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=20220113175417.5523-2-german.gomez@arm.com \
--to=german.gomez@arm.com \
--cc=james.clark@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-eng@arm.com \
--cc=linux-kernel@vger.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®