summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/mem-phys-addr.py
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2021-04-07 20:54:16 +0300
committerMarc Zyngier <maz@kernel.org>2021-04-09 20:26:25 +0300
commit85d703746154cdc6794b6654b587b0b0354c97e9 (patch)
tree9c0ead3a383924403deedb0d0acc75b7afb9a55c /tools/perf/scripts/python/mem-phys-addr.py
parent5b32a53d6d057ab213abae33fc275be844051695 (diff)
downloadlinux-85d703746154cdc6794b6654b587b0b0354c97e9.tar.xz
KVM: arm64: Fully zero the vcpu state on reset
On vcpu reset, we expect all the registers to be brought back to their initial state, which happens to be a bunch of zeroes. However, some recent commit broke this, and is now leaving a bunch of registers (such as the FP state) with whatever was left by the guest. My bad. Zero the reset of the state (32bit SPSRs and FPSIMD state). Cc: stable@vger.kernel.org Fixes: e47c2055c68e ("KVM: arm64: Make struct kvm_regs userspace-only") Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions