Re: [PATCH v4 08/15] KVM: s390: interfaces to (de)configure guest's AP matrix

Tony Krowiak
2018-05-03T14:41:39Z

On 05/02/2018 10:57 AM, Pierre Morel wrote:
> On 25/04/2018 18:21, Tony Krowiak wrote:
>> On 04/23/2018 09:46 AM, Pierre Morel wrote:
>>> On 15/04/2018 23:22, Tony Krowiak wrote:
>>>> Provides interfaces to assign AP adapters, usage domains
>>>> and control domains to a KVM guest.
>>>>
> ...
>>>> +/**
>>>> + * kvm_ap_matrix_create
>>>> + *
>>>> + * Create an AP matrix to hold a configuration of AP adapters,
>>>> domains and
>>>> + * control domains.
>>>> + *
>>>> + * @ap_matrix: holds the matrix that is created
>>>> + *
>>>> + * Returns 0 if the matrix is successfully created. Returns an
>>>> error if an APQN
>>>> + * derived from the cross product of the AP adapter IDs and AP
>>>> queue indexes
>>>> + * comprising the AP matrix is configured for another guest.
>>>> + */
>>>> +int kvm_ap_matrix_create(struct kvm_ap_matrix **ap_matrix);
>>>
>>> why not simply return the pointer?
>>
>> The function returns a value indicating the reason a matrix could not
>> be created.
>> Returning a NULL pointer provides no clue as to why the call failed.
>
> That is why the ERR_PTR exist :)

The point it moot, I'm getting rid of this function call and including the
struct kvm_ap_matrix as a static member of the parent struct ap_matrix_mdev
and not a pointer.

>
>
>
> ...
>>>> + * Returns 0 if the APQNs are valid, otherwise; returns -EBUSY.
>>>> + */
>>>> +static int kvm_ap_validate_queue_sharing(struct kvm *kvm,
>>>> + struct kvm_ap_matrix *matrix)
>>>> +{
>>>> + struct kvm *vm;
>>>> + unsigned long *apm, *aqm;
>>>> + unsigned long apid, apqi;
>>>> +
>>>> +
>>>> + /* No other VM may share an AP Queue with the input VM */
>>>
>>> I wonder if these functions and structures should really belong to KVM.
>>> The only have sense with the VFIO driver.
>>> My opinion is that they belong there, in the VFIO driver code.
>>
>> I disagree for two reasons:
>>
>> 1. The vfio_ap driver should not have to know how to configure the KVM
>> guest's matrix nor anything else about KVM for that matter.
>>
>> 2. The interfaces and structures defined in kvm-ap.h and implemented
>> in kvm-ap.c don't have anything to do with VFIO and can stand alone
>> to be used by any client code to configure a guest's matrix.
>
> Doing this you will have to change KVM if the AP VFIO matrix protocol
> to access the queues change.
> i.e. suppose some day the queues may be shared between guests.
> ...

The kvm_ap_configure_matrix(kvm, matrix) interface configures the APM,
AQM and ADM in the
guest's CRYCB which implies AP instructions are being interpreted. There
is nothing in SIE
precluding the sharing of AP queues between guests using SIE to
interpret AP instructions,
it is my opinion - along with several others - that this is not
advisable given the
results are not predictable, not to mention the security concerns. If
the protocol to access
queues changes, then we create a different interface. The other option
is to include a flag
on the kvm_ap_configure_matrix(kvm, matrix) interface to indicate
whether sharing is
allowed. I don't like this, because we have no way of knowing if the
caller has taken the
proper care to ensure the VM sharing the queue should be allowed access.
Besides, when
queue sharing is implemented, it is my opinion that we will intercept
the AP instructions
and the matrix will not be configured in the CRYCB. I stick by my
response above.

>
>>>> +static int kvm_ap_matrix_apm_create(struct kvm_ap_matrix *ap_matrix,
>>>> + struct ap_config_info *config)
>>>> +{
>>>> + int apm_max = (config && config->apxa) ? config->Na + 1 : 16;
>>>
>>> At this moment you already know the format of the crycb.
>>
>> How?
>
> you calculated this in kvm_ap_build_crycbd() which is called from
> kvm_s390_crypto_init()
> itself called from kvm_arch_init_vm().
> It is when starting the VM.

This structure is used by the vfio_ap driver to store the mediated
matrix device's matrix
configuration as well as to configure the CRYCB. The mediated device's
matrix is
configured before the guest is started ... it is the means for
configuring the guest's
matrix after all. The bottom line is, this function will be called long
before the
kvm_ap_build_crycbd() function is called.

Having said that, I am including the struct kvm_ap_matrix as a static
field in
struct ap_matrix_mdev - i.e., not a pointer. Consequently, the apm_max,
aqm_max
and adm_max fields will be set by the driver when the mediated matrix
device is
created.

>
>
> kvm_ap_matrix_apm_create() is called much later when realizing the device

The kvm_ap_matrix_apm_create() is called by the kvm_ap_matrix_create()
which is called when
the mediated matrix device is created - i.e., the vfio_ap_mdev_create()
function is vfio_ap_ops.c.
The mediated device is created when the UUID is written to the sysfs
create file. The mediated
device is used when the guest is started to configure it's CRYCB, so the
kvm_ap_matrix_apm_create()
is called long before the device is realized.

Again the point is moot because I am getting rid of the dynamic
allocation of struct kvm_ap_matrix.

>
>
> ...
>
>
>