KVM: s390: interrupt: Fix single-stepping into interrupt handlers
authorIlya Leoshkevich <iii@linux.ibm.com>
Tue, 25 Jul 2023 14:37:16 +0000 (16:37 +0200)
committerJanosch Frank <frankja@linux.ibm.com>
Mon, 28 Aug 2023 09:24:19 +0000 (09:24 +0000)
commit16631c42e6ff4f5acf30998fda6c2ea09d1adbfe
treebb600074ead2b159ebe0e1f99297aed0fd9db50e
parentede6d0b2031e045f0a0e4515e4567828d87fd3ef
KVM: s390: interrupt: Fix single-stepping into interrupt handlers

After single-stepping an instruction that generates an interrupt, GDB
ends up on the second instruction of the respective interrupt handler.

The reason is that vcpu_pre_run() manually delivers the interrupt, and
then __vcpu_run() runs the first handler instruction using the
CPUSTAT_P flag. This causes a KVM_SINGLESTEP exit on the second handler
instruction.

Fix by delaying the KVM_SINGLESTEP exit until after the manual
interrupt delivery.

Acked-by: David Hildenbrand <david@redhat.com>
Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
Message-ID: <20230725143857.228626-2-iii@linux.ibm.com>
Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
arch/s390/kvm/interrupt.c
arch/s390/kvm/kvm-s390.c