diff options
| author | Marc Zyngier <maz@kernel.org> | 2021-04-07 18:54:16 +0100 |
|---|---|---|
| committer | Marc Zyngier <maz@kernel.org> | 2021-04-09 18:26:25 +0100 |
| commit | 85d703746154cdc6794b6654b587b0b0354c97e9 (patch) | |
| tree | 9c0ead3a383924403deedb0d0acc75b7afb9a55c /tools/perf/scripts/python/bin | |
| parent | KVM: arm64: Clarify vcpu reset behaviour (diff) | |
| download | linux-85d703746154cdc6794b6654b587b0b0354c97e9.tar.gz linux-85d703746154cdc6794b6654b587b0b0354c97e9.zip | |
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/bin')
0 files changed, 0 insertions, 0 deletions