summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/gecko.py
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2025-01-17 14:06:33 +0300
committerMarc Zyngier <maz@kernel.org>2025-01-17 14:06:33 +0300
commit3643b334aa8f02ddcedc093d7de623378192da06 (patch)
tree5466cc2bfef2f0b4d46c6c62d223fd8e9f193e74 /tools/perf/scripts/python/gecko.py
parent946904e728eaf1d505d396516bed1eecac02939b (diff)
parent36f998de853cfad60508dfdfb41c9c40a2245f19 (diff)
downloadlinux-3643b334aa8f02ddcedc093d7de623378192da06.tar.xz
Merge branch kvm-arm64/nv-resx-fixes-6.14 into kvmarm-master/next
* kvm-arm64/nv-resx-fixes-6.14: : . : Fixes for NV sysreg accessors. From the cover letter: : : "Joey recently reported that some rather basic tests were failing on : NV, and managed to track it down to critical register fields (such as : HCR_EL2.E2H) not having their expect value. : : Further investigation has outlined a couple of critical issues: : : - Evaluating HCR_EL2.E2H must always be done with a sanitising : accessor, no ifs, no buts. Given that KVM assumes a fixed value for : this bit, we cannot leave it to the guest to mess with. : : - Resetting the sysreg file must result in the RESx bits taking : effect. Otherwise, we may end-up making the wrong decision (see : above), and we definitely expose invalid values to the guest. Note : that because we compute the RESx masks very late in the VM setup, we : need to apply these masks at that particular point as well. : [...]" : . KVM: arm64: nv: Apply RESx settings to sysreg reset values KVM: arm64: nv: Always evaluate HCR_EL2 using sanitising accessors Signed-off-by: Marc Zyngier <maz@kernel.org> # Conflicts: # arch/arm64/kvm/nested.c
Diffstat (limited to 'tools/perf/scripts/python/gecko.py')
0 files changed, 0 insertions, 0 deletions