summaryrefslogtreecommitdiffstats
path: root/crypto/poly1305_generic.c
diff options
context:
space:
mode:
authorAndrew Jones <drjones@redhat.com>2019-08-22 13:03:05 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-09-10 10:35:24 +0100
commit7f134d569e1ab172d37de5c22e5bb000a036ac4c (patch)
tree51bb1041f8109f0ca4f448290ffdb1137d31d243 /crypto/poly1305_generic.c
parent39c62cdaa2d41ea9007b80b6a4bf04a69d5ba32c (diff)
downloadlinux-stable-7f134d569e1ab172d37de5c22e5bb000a036ac4c.tar.gz
linux-stable-7f134d569e1ab172d37de5c22e5bb000a036ac4c.tar.bz2
linux-stable-7f134d569e1ab172d37de5c22e5bb000a036ac4c.zip
KVM: arm/arm64: Only skip MMIO insn once
[ Upstream commit 2113c5f62b7423e4a72b890bd479704aa85c81ba ] If after an MMIO exit to userspace a VCPU is immediately run with an immediate_exit request, such as when a signal is delivered or an MMIO emulation completion is needed, then the VCPU completes the MMIO emulation and immediately returns to userspace. As the exit_reason does not get changed from KVM_EXIT_MMIO in these cases we have to be careful not to complete the MMIO emulation again, when the VCPU is eventually run again, because the emulation does an instruction skip (and doing too many skips would be a waste of guest code :-) We need to use additional VCPU state to track if the emulation is complete. As luck would have it, we already have 'mmio_needed', which even appears to be used in this way by other architectures already. Fixes: 0d640732dbeb ("arm64: KVM: Skip MMIO insn after emulation") Acked-by: Mark Rutland <mark.rutland@arm.com> Signed-off-by: Andrew Jones <drjones@redhat.com> Signed-off-by: Marc Zyngier <maz@kernel.org> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'crypto/poly1305_generic.c')
0 files changed, 0 insertions, 0 deletions