On 08/20/2018 04:41 PM, David Hildenbrand wrote:
+ if (test_kvm_cpu_feat(vcpu->kvm, KVM_S390_VM_CPU_FEAT_AP))
+ vcpu->arch.sie_block->eca |= ECA_APIE;
- vcpu->arch.sie_block->crycbd = vcpu->kvm->arch.crypto.crycbd;
+ /* If MSAX3 is installed on the guest, set up pro
>>
>>> + if (test_kvm_cpu_feat(vcpu->kvm, KVM_S390_VM_CPU_FEAT_AP))
>>> + vcpu->arch.sie_block->eca |= ECA_APIE;
>>>
>>> - vcpu->arch.sie_block->crycbd = vcpu->kvm->arch.crypto.crycbd;
>>> + /* If MSAX3 is installed on the guest, set up protected key support */
>>> + if (test_k
On 08/20/2018 12:41 PM, David Hildenbrand wrote:
On 13.08.2018 23:48, Tony Krowiak wrote:
From: Tony Krowiak
This patch refactors the code that initializes and sets up the
crypto configuration for a guest. The following changes are
implemented via this patch:
1. Prior to the introduction of A
On 13.08.2018 23:48, Tony Krowiak wrote:
> From: Tony Krowiak
>
> This patch refactors the code that initializes and sets up the
> crypto configuration for a guest. The following changes are
> implemented via this patch:
>
> 1. Prior to the introduction of AP device virtualization, it
>was n
From: Tony Krowiak
This patch refactors the code that initializes and sets up the
crypto configuration for a guest. The following changes are
implemented via this patch:
1. Prior to the introduction of AP device virtualization, it
was not necessary to provide guest access to the CRYCB
unle
5 matches
Mail list logo