summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorMark Rutland <mark.rutland@arm.com>2018-10-17 17:42:10 +0100
committerMarc Zyngier <marc.zyngier@arm.com>2018-10-17 18:32:46 +0100
commitda5a3ce66b8bb51b0ea8a89f42aac153903f90fb (patch)
tree474db21720fe65162b016935cb55f6ec41287dbf /Documentation
parentfd2ef358282c849c193aa36dadbf4f07f7dcd29b (diff)
downloadlinux-da5a3ce66b8bb51b0ea8a89f42aac153903f90fb.tar.gz
linux-da5a3ce66b8bb51b0ea8a89f42aac153903f90fb.tar.bz2
linux-da5a3ce66b8bb51b0ea8a89f42aac153903f90fb.zip
KVM: arm64: Fix caching of host MDCR_EL2 value
At boot time, KVM stashes the host MDCR_EL2 value, but only does this when the kernel is not running in hyp mode (i.e. is non-VHE). In these cases, the stashed value of MDCR_EL2.HPMN happens to be zero, which can lead to CONSTRAINED UNPREDICTABLE behaviour. Since we use this value to derive the MDCR_EL2 value when switching to/from a guest, after a guest have been run, the performance counters do not behave as expected. This has been observed to result in accesses via PMXEVTYPER_EL0 and PMXEVCNTR_EL0 not affecting the relevant counters, resulting in events not being counted. In these cases, only the fixed-purpose cycle counter appears to work as expected. Fix this by always stashing the host MDCR_EL2 value, regardless of VHE. Cc: Christopher Dall <christoffer.dall@arm.com> Cc: James Morse <james.morse@arm.com> Cc: Will Deacon <will.deacon@arm.com> Cc: stable@vger.kernel.org Fixes: 1e947bad0b63b351 ("arm64: KVM: Skip HYP setup when already running in HYP") Tested-by: Robin Murphy <robin.murphy@arm.com> Signed-off-by: Mark Rutland <mark.rutland@arm.com> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions