public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: Heiko Carstens <hca@linux.ibm.com>, KVM <kvm@vger.kernel.org>,
	Janosch Frank <frankja@linux.ibm.com>,
	David Hildenbrand <david@redhat.com>,
	linux-s390 <linux-s390@vger.kernel.org>,
	Thomas Huth <thuth@redhat.com>, Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Marc Hartmayer <mhartmay@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [PATCH 1/1] KVM: s390: fix LPSWEY handling
Date: Fri, 28 Jun 2024 17:50:40 +0200	[thread overview]
Message-ID: <d0d1f6e1-34d3-4770-87d2-1597af9faa90@linux.ibm.com> (raw)
In-Reply-To: <20240628172259.1e172f35@p-imbrenda.boeblingen.de.ibm.com>

Am 28.06.24 um 17:22 schrieb Claudio Imbrenda:
> On Fri, 28 Jun 2024 16:53:20 +0200
> Christian Borntraeger <borntraeger@linux.ibm.com> wrote:
> 
>> Am 27.06.24 um 11:57 schrieb Heiko Carstens:
>>> On Thu, Jun 27, 2024 at 11:05:20AM +0200, Christian Borntraeger wrote:
>>>> in rare cases, e.g. for injecting a machine check we do intercept all
>>>> load PSW instructions via ICTL_LPSW. With facility 193 a new variant
>>>> LPSWEY was added. KVM needs to handle that as well.
>>>>
>>>> Fixes: a3efa8429266 ("KVM: s390: gen_facilities: allow facilities 165, 193, 194 and 196")
>>>> Reported-by: Marc Hartmayer <mhartmay@linux.ibm.com>
>>>> Signed-off-by: Christian Borntraeger <borntraeger@linux.ibm.com>
>>>> ---
>>>>    arch/s390/include/asm/kvm_host.h |  1 +
>>>>    arch/s390/kvm/kvm-s390.c         |  1 +
>>>>    arch/s390/kvm/kvm-s390.h         | 16 ++++++++++++++++
>>>>    arch/s390/kvm/priv.c             | 32 ++++++++++++++++++++++++++++++++
>>>>    4 files changed, 50 insertions(+)
>>>
>>> ...
>>>    
>>>> +static inline u64 kvm_s390_get_base_disp_siy(struct kvm_vcpu *vcpu, u8 *ar)
>>>> +{
>>>> +	u32 base1 = vcpu->arch.sie_block->ipb >> 28;
>>>> +	u32 disp1 = ((vcpu->arch.sie_block->ipb & 0x0fff0000) >> 16) +
> 
> long disp1 = ...
> 
>>>> +			((vcpu->arch.sie_block->ipb & 0xff00) << 4);
>>>> +
>>>> +	/* The displacement is a 20bit _SIGNED_ value */
>>>> +	if (disp1 & 0x80000)
>>>> +		disp1+=0xfff00000;
> 
> disp1 = sign_extend64(disp1, 20);

Hmm, right. I was just looking at the return statement, but here it is clearly better.

Will send a v2

  reply	other threads:[~2024-06-28 15:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27  9:05 [PATCH 1/1] KVM: s390: fix LPSWEY handling Christian Borntraeger
2024-06-27  9:23 ` Claudio Imbrenda
2024-06-27  9:40   ` Christian Borntraeger
2024-06-27  9:44 ` Thomas Huth
2024-06-27  9:49   ` Christian Borntraeger
2024-06-27  9:57 ` Heiko Carstens
2024-06-28 14:53   ` Christian Borntraeger
2024-06-28 15:02     ` Heiko Carstens
2024-06-28 15:22     ` Claudio Imbrenda
2024-06-28 15:50       ` Christian Borntraeger [this message]
2024-06-28 16:55       ` Christian Borntraeger

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=d0d1f6e1-34d3-4770-87d2-1597af9faa90@linux.ibm.com \
    --to=borntraeger@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=david@redhat.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=mhartmay@linux.ibm.com \
    --cc=svens@linux.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox