summaryrefslogtreecommitdiff
path: root/drivers/memstick
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2019-10-08 17:09:55 +0300
committerMarc Zyngier <maz@kernel.org>2019-10-20 12:47:07 +0300
commit725ce66979fb6da5c1aec5b064d0871bedc23bf7 (patch)
tree160b07ae49fd048279fc3a8684fafc17de14bbd4 /drivers/memstick
parent6f16371453476fd094760ea3d6f00144e9ae3057 (diff)
downloadlinux-725ce66979fb6da5c1aec5b064d0871bedc23bf7.tar.xz
KVM: arm64: pmu: Set the CHAINED attribute before creating the in-kernel event
The current convention for KVM to request a chained event from the host PMU is to set bit[0] in attr.config1 (PERF_ATTR_CFG1_KVM_PMU_CHAINED). But as it turns out, this bit gets set *after* we create the kernel event that backs our virtual counter, meaning that we never get a 64bit counter. Moving the setting to an earlier point solves the problem. Fixes: 80f393a23be6 ("KVM: arm/arm64: Support chained PMU counters") Reviewed-by: Andrew Murray <andrew.murray@arm.com> Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'drivers/memstick')
0 files changed, 0 insertions, 0 deletions