From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Janosch Frank <frankja@linux.vnet.ibm.com>,
KVM <kvm@vger.kernel.org>, David Hildenbrand <david@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Qian Cai <cailca@icloud.com>, Pierre Morel <pmorel@linux.ibm.com>,
Tony Krowiak <akrowiak@linux.ibm.com>
Subject: Re: [PATCH] KVM: s390: Remove false WARN_ON_ONCE for the PQAP instruction
Date: Tue, 5 May 2020 09:55:36 +0200 [thread overview]
Message-ID: <f3512a63-91dc-ab9a-a9ab-3e2a6e24fea3@de.ibm.com> (raw)
In-Reply-To: <20200505095332.528254e5.cohuck@redhat.com>
On 05.05.20 09:53, Cornelia Huck wrote:
> On Tue, 5 May 2020 09:35:25 +0200
> Christian Borntraeger <borntraeger@de.ibm.com> wrote:
>
>> In LPAR we will only get an intercept for FC==3 for the PQAP
>> instruction. Running nested under z/VM can result in other intercepts as
>> well, for example PQAP(QCI). So the WARN_ON_ONCE is not right. Let
>> us simply remove it.
>
> While I agree with removing the WARN_ON_ONCE, I'm wondering why z/VM
> gives us intercepts for those fcs... is that just a result of nesting
> (or the z/VM implementation), or is there anything we might want to do?
Yes nesting.
The ECA bit for interpretion is an effective one. So if the ECA bit is off
in z/VM (no crypto cards) our ECA bit is basically ignored as these bits
are ANDed.
I asked Tony to ask the z/VM team if that is the case here.
>
>>
>> Cc: Pierre Morel <pmorel@linux.ibm.com>
>> Cc: Tony Krowiak <akrowiak@linux.ibm.com>
>> Reported-by: Qian Cai <cailca@icloud.com>
>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>> ---
>> arch/s390/kvm/priv.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/s390/kvm/priv.c b/arch/s390/kvm/priv.c
>> index 69a824f9ef0b..bbe46c6aedbf 100644
>> --- a/arch/s390/kvm/priv.c
>> +++ b/arch/s390/kvm/priv.c
>> @@ -626,10 +626,12 @@ static int handle_pqap(struct kvm_vcpu *vcpu)
>> * available for the guest are AQIC and TAPQ with the t bit set
>> * since we do not set IC.3 (FIII) we currently will only intercept
>> * the AQIC function code.
>> + * Note: running nested under z/VM can result in intercepts, e.g.
>
> s/intercepts/intercepts for other function codes/
>
>> + * for PQAP(QCI). We do not support this and bail out.
>> */
>> reg0 = vcpu->run->s.regs.gprs[0];
>> fc = (reg0 >> 24) & 0xff;
>> - if (WARN_ON_ONCE(fc != 0x03))
>> + if (fc != 0x03)
>> return -EOPNOTSUPP;
>>
>> /* PQAP instruction is allowed for guest kernel only */
>
next prev parent reply other threads:[~2020-05-05 7:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 7:35 [PATCH] KVM: s390: Remove false WARN_ON_ONCE for the PQAP instruction Christian Borntraeger
2020-05-05 7:53 ` Cornelia Huck
2020-05-05 7:55 ` Christian Borntraeger [this message]
2020-05-05 8:04 ` David Hildenbrand
2020-05-05 8:27 ` Christian Borntraeger
2020-05-05 8:28 ` David Hildenbrand
2020-05-05 8:33 ` Cornelia Huck
2020-05-05 12:18 ` Pierre Morel
2020-05-05 12:31 ` Christian Borntraeger
2020-05-05 8:21 ` Cornelia Huck
2020-05-05 22:34 ` Tony Krowiak
2020-05-06 6:08 ` Christian Borntraeger
2020-05-06 23:29 ` Tony Krowiak
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=f3512a63-91dc-ab9a-a9ab-3e2a6e24fea3@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=akrowiak@linux.ibm.com \
--cc=cailca@icloud.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pmorel@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;
as well as URLs for NNTP newsgroup(s).