From: Heiko Carstens <hca@linux.ibm.com>
To: Christian Borntraeger <borntraeger@linux.ibm.com>
Cc: KVM <kvm@vger.kernel.org>, Janosch Frank <frankja@linux.ibm.com>,
David Hildenbrand <david@kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
Thomas Huth <thuth@redhat.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>
Subject: Re: [PATCH v2] KVM: s390: vsie: Avoid injecting machine check on signal
Date: Mon, 16 Mar 2026 14:07:02 +0100 [thread overview]
Message-ID: <20260316130702.17080Dcf-hca@linux.ibm.com> (raw)
In-Reply-To: <d291035f-8bf1-493c-a629-5852a1e65caa@linux.ibm.com>
On Mon, Mar 16, 2026 at 01:35:59PM +0100, Christian Borntraeger wrote:
> Am 16.03.26 um 13:25 schrieb Christian Borntraeger:
> I guess we should still add something like
>
> --- a/arch/s390/kvm/vsie.c
> +++ b/arch/s390/kvm/vsie.c
> @@ -1123,6 +1123,7 @@ static int do_vsie_run(struct kvm_vcpu *vcpu, struct vsie_page *vsie_page, struc
> struct kvm_s390_sie_block *scb_s = &vsie_page->scb_s;
> struct kvm_s390_sie_block *scb_o = vsie_page->scb_o;
> int guest_bp_isolation;
> + int sie_return = SIE64_RETURN_OK;
> int rc = 0;
> handle_last_fault(vcpu, vsie_page, sg);
> @@ -1163,7 +1164,7 @@ static int do_vsie_run(struct kvm_vcpu *vcpu, struct vsie_page *vsie_page, struc
> goto xfer_to_guest_mode_check;
> }
> guest_timing_enter_irqoff();
> - rc = kvm_s390_enter_exit_sie(scb_s, vcpu->run->s.regs.gprs, sg->asce.val);
> + sie_return = kvm_s390_enter_exit_sie(scb_s, vcpu->run->s.regs.gprs, sg->asce.val);
> guest_timing_exit_irqoff();
> local_irq_enable();
> }
> @@ -1178,7 +1179,7 @@ static int do_vsie_run(struct kvm_vcpu *vcpu, struct vsie_page *vsie_page, struc
> kvm_vcpu_srcu_read_lock(vcpu);
> - if (rc == SIE64_RETURN_MCCK) {
> + if (sie_return == SIE64_RETURN_MCCK) {
> kvm_s390_reinject_machine_check(vcpu, &vsie_page->mcck_info);
> return 0;
Yes, this looks better and makes the code more understandable.
next prev parent reply other threads:[~2026-03-16 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 12:25 [PATCH v2] KVM: s390: vsie: Avoid injecting machine check on signal Christian Borntraeger
2026-03-16 12:35 ` Christian Borntraeger
2026-03-16 13:07 ` Heiko Carstens [this message]
2026-03-16 13:05 ` Heiko Carstens
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=20260316130702.17080Dcf-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@kernel.org \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=thuth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.