public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Eric Farman <farman@linux.ibm.com>,
	Janosch Frank <frankja@linux.ibm.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>,
	David Hildenbrand <david@redhat.com>
Cc: Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>,
	kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH] KVM: s390: only deliver the set service event bits
Date: Wed, 7 Feb 2024 17:20:37 +0100	[thread overview]
Message-ID: <044e0a7f-5718-455f-a22d-fa8dc7aaa69b@linux.ibm.com> (raw)
In-Reply-To: <20240205214300.1018522-1-farman@linux.ibm.com>



Am 05.02.24 um 22:43 schrieb Eric Farman:
> The SCLP driver code masks off the last two bits of the parameter [1]
> to determine if a read is required, but doesn't care about the
> contents of those bits. Meanwhile, the KVM code that delivers
> event interrupts masks off those two bits but sends both to the
> guest, even if only one was specified by userspace [2].
> 
> This works for the driver code, but it means any nuances of those
> bits gets lost. Use the event pending mask as an actual mask, and
> only send the bit(s) that were specified in the pending interrupt.
> 
> [1] Linux: sclp_interrupt_handler() (drivers/s390/char/sclp.c:658)
> [2] QEMU: service_interrupt() (hw/s390x/sclp.c:360..363)
> 
> Fixes: 0890ddea1a90 ("KVM: s390: protvirt: Add SCLP interrupt handling")
> Signed-off-by: Eric Farman <farman@linux.ibm.com>

makes sense

Reviewed-by: Christian Borntraeger <borntraeger@linux.ibm.com>


> ---
>   arch/s390/kvm/interrupt.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/s390/kvm/interrupt.c b/arch/s390/kvm/interrupt.c
> index fc4007cc067a..20e080e9150b 100644
> --- a/arch/s390/kvm/interrupt.c
> +++ b/arch/s390/kvm/interrupt.c
> @@ -1031,7 +1031,7 @@ static int __must_check __deliver_service_ev(struct kvm_vcpu *vcpu)
>   		return 0;
>   	}
>   	ext = fi->srv_signal;
> -	/* only clear the event bit */
> +	/* only clear the event bits */
>   	fi->srv_signal.ext_params &= ~SCCB_EVENT_PENDING;
>   	clear_bit(IRQ_PEND_EXT_SERVICE_EV, &fi->pending_irqs);
>   	spin_unlock(&fi->lock);
> @@ -1041,7 +1041,7 @@ static int __must_check __deliver_service_ev(struct kvm_vcpu *vcpu)
>   	trace_kvm_s390_deliver_interrupt(vcpu->vcpu_id, KVM_S390_INT_SERVICE,
>   					 ext.ext_params, 0);
>   
> -	return write_sclp(vcpu, SCCB_EVENT_PENDING);
> +	return write_sclp(vcpu, ext.ext_params & SCCB_EVENT_PENDING);
>   }
>   
>   static int __must_check __deliver_pfault_done(struct kvm_vcpu *vcpu)

  reply	other threads:[~2024-02-07 16:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 21:43 [PATCH] KVM: s390: only deliver the set service event bits Eric Farman
2024-02-07 16:20 ` Christian Borntraeger [this message]
2024-02-21 15:36 ` Janosch Frank
2024-02-22  9:40 ` Janosch Frank

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=044e0a7f-5718-455f-a22d-fa8dc7aaa69b@linux.ibm.com \
    --to=borntraeger@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@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