Re: [PATCH v4 1/7] s390: ap: kvm: add PQAP interception for AQIC

[Pierre Morel]

On 25/02/2019 19:36, Tony Krowiak wrote:
> On 2/22/19 10:29 AM, Pierre Morel wrote:
> > We prepare the interception of the PQAP/AQIC instruction for
> > the case the AQIC facility is enabled in the guest.
> >
> > We add a callback inside the KVM arch structure for s390 for
> > a VFIO driver to handle a specific response to the PQAP
> > instruction with the AQIC command.
> >
> > We inject the correct exceptions from inside KVM for the case the
> > callback is not initialized, which happens when the vfio_ap driver
> > is not loaded.
> >
> > If the callback has been setup we call it.
> > If not we setup an answer considering that no queue is available
> > for the guest when no callback has been setup.
> >
> > We do consider the responsability of the driver to always initialize
> > the PQAP callback if it defines queues by initializing the CRYCB for
> > a guest.
> >
> > Signed-off-by: Pierre Morel <pmorel@xxxxxxxxxxxxx>

...snip...

> > @@ -592,6 +593,55 @@ static int handle_io_inst(struct kvm_vcpu *vcpu)
> > ÂÂÂÂÂ }
> > Â }
> > +/*
> > + * handle_pqap: Handling pqap interception
> > + * @vcpu: the vcpu having issue the pqap instruction
> > + *
> > + * We now support PQAP/AQIC instructions and we need to correctly
> > + * answer the guest even if no dedicated driver's hook is available.
> > + *
> > + * The intercepting code calls a dedicated callback for this instruction
> > + * if a driver did register one in the CRYPTO satellite of the
> > + * SIE block.
> > + *
> > + * For PQAP/AQIC instructions only, verify privilege and specifications.
> > + *
> > + * If no callback available, the queues are not available, return 
> > this to
> > + * the caller.
> > + * Else return the value returned by the callback.
> > + */
> > +static int handle_pqap(struct kvm_vcpu *vcpu)
> > +{
> > +ÂÂÂ uint8_t fc;
> > +ÂÂÂ struct ap_queue_status status = {};
> > +
> > +ÂÂÂ /* Verify that the AP instruction are available */
> > +ÂÂÂ if (!ap_instructions_available())
> > +ÂÂÂÂÂÂÂ return -EOPNOTSUPP;
>
> How can the guest even execute an AP instruction if the AP instructions
> are not available? If the AP instructions are not available on the host,
> they will not be available on the guest (i.e., CPU model feature
> S390_FEAT_AP will not be set). I suppose it doesn't hurt to check this
> here given QEMU may not be the only client.
>
> > +ÂÂÂ /* Verify that the guest is allowed to use AP instructions */
> > +ÂÂÂ if (!(vcpu->arch.sie_block->eca & ECA_APIE))
> > +ÂÂÂÂÂÂÂ return -EOPNOTSUPP;
> > +ÂÂÂ /* Verify that the function code is AQIC */
> > +ÂÂÂ fc = vcpu->run->s.regs.gprs[0] >> 24;
> > +ÂÂÂ if (fc != 0x03)
> > +ÂÂÂÂÂÂÂ return -EOPNOTSUPP;
>
> You must have missed my suggestion to move this to the
> vcpu->kvm->arch.crypto.pqap_hook(vcpu) in the following responses:

Please consider what happen if the vfio_ap module is not loaded.

> Message ID <342ffd56-b73a-b1f4-004d-de2c4aeef729@xxxxxxxxxxxxx>
> Message ID <e04f0c8b-2fd9-1846-334a-faa48e0e051e@xxxxxxxxxxxxx>
>
> You previously stated:
>
>  ÂÂ "QEMU and KVM can both accept PQAP/AQIC even if the vfio_ap driver is
>  ÂÂÂ not loaded. However now that the guest officially get the PQAP/AQIC
>  ÂÂÂ instruction we need to handle the specification and operation
>  ÂÂÂ exceptions inside KVM _before_ testing and even calling the driver
>  ÂÂÂ hook.
>
>  ÂÂÂ I will make the changes in the next iteration."

Still seems right to me, and is done is this patch.
Isn't it?

> I don't know what any of the above has to do with checking FC=0x03? If
> that check is moved to the pqap handler hook, it can just as well return
> -EOPNOTSUPP. In fact, down below you do this:
>
>  ÂÂÂÂreturn vcpu->kvm->arch.crypto.pqap_hook(vcpu);
>
> If the RC=0x03 check fails in the hook, it will return -EOPNOTSUPP just
> like above. None of this is critical, but the parsing of the register
> values for the PQAP(AQIC) function ought to be done in the code that
> handles the PQAP instruction IMHO.


This interception code must handle the PQAP/AQIC instruction when the 
hook is not used and should not modify the handling for other PQAP 
instructions.
We can not move anything inside the hook that must be always done.

Regards,
Pierre

--
Pierre Morel
Linux/KVM/QEMU in BÃblingen - Germany