summaryrefslogtreecommitdiffstats
path: root/tools/perf/util/scripting-engines/trace-event-perl.c
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2022-11-24 10:40:02 +0000
committerMarc Zyngier <maz@kernel.org>2022-11-28 14:04:08 +0000
commit292e8f1494764ac46dd1b7dd46fa317db691436c (patch)
treecebfe724432816d5fbfac1a2b332451bc1860fd3 /tools/perf/util/scripting-engines/trace-event-perl.c
parent86815735aa571d493cf5768cad5fa8e6fd9c7ba8 (diff)
downloadlinux-292e8f1494764ac46dd1b7dd46fa317db691436c.tar.gz
linux-292e8f1494764ac46dd1b7dd46fa317db691436c.tar.bz2
linux-292e8f1494764ac46dd1b7dd46fa317db691436c.zip
KVM: arm64: PMU: Simplify PMCR_EL0 reset handling
Resetting PMCR_EL0 is a pretty involved process that includes poisoning some of the writable bits, just because we can. It makes it hard to reason about about what gets configured, and just resetting things to 0 seems like a much saner option. Reduce reset_pmcr() to just preserving PMCR_EL0.N from the host, and setting PMCR_EL0.LC if we don't support AArch32. Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-perl.c')
0 files changed, 0 insertions, 0 deletions