lkml.org 
[lkml]   [2018]   [Aug]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH v9 19/22] KVM: s390: Clear Crypto Control Block when using vSIE
    Date
    From: Pierre Morel <pmorel@linux.ibm.com>

    When we clear the Crypto Control Block (CRYCB) used by a guest
    level 2, the vSIE shadow CRYCB for guest level 3 must be updated
    before the guest uses it.

    We achieve this by using the KVM_REQ_VSIE_RESTART synchronous
    request for each vCPU belonging to the guest to force the reload
    of the shadow CRYCB before rerunning the guest level 3.

    Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
    Signed-off-by: Tony Krowiak <akrowiak@linux.ibm.com>
    ---
    arch/s390/kvm/kvm-s390.c | 2 ++
    1 files changed, 2 insertions(+), 0 deletions(-)

    diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
    index 8d8a65a..1e8cb67 100644
    --- a/arch/s390/kvm/kvm-s390.c
    +++ b/arch/s390/kvm/kvm-s390.c
    @@ -1929,6 +1929,8 @@ void kvm_arch_crypto_clear_masks(struct kvm *kvm)
    memset(&kvm->arch.crypto.crycb->apcb1, 0,
    sizeof(kvm->arch.crypto.crycb->apcb1));

    + /* recreate the shadow crycb for each vcpu */
    + kvm_s390_sync_request_broadcast(kvm, KVM_REQ_VSIE_RESTART);
    kvm_s390_vcpu_unblock_all(kvm);
    mutex_unlock(&kvm->lock);
    }
    --
    1.7.1
    \
     
     \ /
      Last update: 2018-08-13 23:50    [W:2.683 / U:0.036 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site