Mark Rutland bd7d95cafb arm64: KVM: Consistently advance singlestep when emulating instructions ... When we emulate a guest instruction, we don't advance the hardware singlestep state machine, and thus the guest will receive a software step exception after a next instruction which is not emulated by the host. We bodge around this in an ad-hoc fashion. Sometimes we explicitly check whether userspace requested a single step, and fake a debug exception from within the kernel. Other times, we advance the HW singlestep state rely on the HW to generate the exception for us. Thus, the observed step behaviour differs for host and guest. Let's make this simpler and consistent by always advancing the HW singlestep state machine when we skip an instruction. Thus we can rely on the hardware to generate the singlestep exception for us, and never need to explicitly check for an active-pending step, nor do we need to fake a debug exception from the guest. Cc: Peter Maydell <peter.maydell@linaro.org> Reviewed-by: Alex Bennée <alex.bennee@linaro.org> Reviewed-by: Christoffer Dall <christoffer.dall@arm.com> Signed-off-by: Mark Rutland <mark.rutland@arm.com> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>		2018-12-18 14:11:37 +00:00
..
timer-sr.c	KVM: arm64: Remove noop calls to timer save/restore from VHE switch	2018-03-19 10:53:14 +00:00
vgic-v3-sr.c	arm64: KVM: Consistently advance singlestep when emulating instructions	2018-12-18 14:11:37 +00:00