From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: Christian Borntraeger <borntraeger@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
Sven Schnelle <svens@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jens Freimann <jfreimann@redhat.com>
Subject: Re: [PATCH v3 1/6] KVM: s390: interrupt: Fix single-stepping into interrupt handlers
Date: Tue, 25 Jul 2023 13:56:54 +0200 [thread overview]
Message-ID: <20230725135654.657f6b74@p-imbrenda> (raw)
In-Reply-To: <20230724094716.91510-2-iii@linux.ibm.com>
On Mon, 24 Jul 2023 11:44:07 +0200
Ilya Leoshkevich <iii@linux.ibm.com> wrote:
> 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>
> Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> ---
> arch/s390/kvm/interrupt.c | 14 ++++++++++++++
> arch/s390/kvm/kvm-s390.c | 4 ++--
> 2 files changed, 16 insertions(+), 2 deletions(-)
>
> diff --git a/arch/s390/kvm/interrupt.c b/arch/s390/kvm/interrupt.c
> index 9bd0a873f3b1..85e39f472bb4 100644
> --- a/arch/s390/kvm/interrupt.c
> +++ b/arch/s390/kvm/interrupt.c
> @@ -1392,6 +1392,7 @@ int __must_check kvm_s390_deliver_pending_interrupts(struct kvm_vcpu *vcpu)
> {
> struct kvm_s390_local_interrupt *li = &vcpu->arch.local_int;
> int rc = 0;
> + bool delivered = false;
> unsigned long irq_type;
> unsigned long irqs;
>
> @@ -1465,6 +1466,19 @@ int __must_check kvm_s390_deliver_pending_interrupts(struct kvm_vcpu *vcpu)
> WARN_ONCE(1, "Unknown pending irq type %ld", irq_type);
> clear_bit(irq_type, &li->pending_irqs);
> }
> + delivered |= !rc;
> + }
> +
> + /*
> + * We delivered at least one interrupt and modified the PC. Force a
> + * singlestep event now.
> + */
> + if (delivered && guestdbg_sstep_enabled(vcpu)) {
> + struct kvm_debug_exit_arch *debug_exit = &vcpu->run->debug.arch;
> +
> + debug_exit->addr = vcpu->arch.sie_block->gpsw.addr;
> + debug_exit->type = KVM_SINGLESTEP;
> + vcpu->guest_debug |= KVM_GUESTDBG_EXIT_PENDING;
> }
>
> set_intercept_indicators(vcpu);
> diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
> index d1e768bcfe1d..0c6333b108ba 100644
> --- a/arch/s390/kvm/kvm-s390.c
> +++ b/arch/s390/kvm/kvm-s390.c
> @@ -4611,7 +4611,7 @@ static int vcpu_pre_run(struct kvm_vcpu *vcpu)
>
> if (!kvm_is_ucontrol(vcpu->kvm)) {
> rc = kvm_s390_deliver_pending_interrupts(vcpu);
> - if (rc)
> + if (rc || guestdbg_exit_pending(vcpu))
> return rc;
> }
>
> @@ -4738,7 +4738,7 @@ static int __vcpu_run(struct kvm_vcpu *vcpu)
>
> do {
> rc = vcpu_pre_run(vcpu);
> - if (rc)
> + if (rc || guestdbg_exit_pending(vcpu))
> break;
>
> kvm_vcpu_srcu_read_unlock(vcpu);
next prev parent reply other threads:[~2023-07-25 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 9:44 [PATCH v3 0/6] KVM: s390: interrupt: Fix stepping into interrupt handlers Ilya Leoshkevich
2023-07-24 9:44 ` [PATCH v3 1/6] KVM: s390: interrupt: Fix single-stepping " Ilya Leoshkevich
2023-07-25 11:56 ` Claudio Imbrenda [this message]
2023-07-24 9:44 ` [PATCH v3 2/6] KVM: s390: interrupt: Fix single-stepping into program " Ilya Leoshkevich
2023-07-25 8:58 ` Claudio Imbrenda
2023-07-24 9:44 ` [PATCH v3 3/6] KVM: s390: interrupt: Fix single-stepping kernel-emulated instructions Ilya Leoshkevich
2023-07-25 12:04 ` Claudio Imbrenda
2023-07-24 9:44 ` [PATCH v3 4/6] KVM: s390: interrupt: Fix single-stepping userspace-emulated instructions Ilya Leoshkevich
2023-07-24 11:31 ` David Hildenbrand
2023-07-25 12:25 ` Claudio Imbrenda
2023-07-24 9:44 ` [PATCH v3 5/6] KVM: s390: interrupt: Fix single-stepping keyless mode exits Ilya Leoshkevich
2023-07-24 9:44 ` [PATCH v3 6/6] KVM: s390: selftests: Add selftest for single-stepping Ilya Leoshkevich
2023-07-25 13:53 ` Claudio Imbrenda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230725135654.657f6b74@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=jfreimann@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox