[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <963fbc8076172bd430621446070cfd6ca8f165b8.camel@redhat.com>
Date: Thu, 02 Nov 2023 20:07:35 +0200
From: Maxim Levitsky <mlevitsk@...hat.com>
To: John Allen <john.allen@....com>, kvm@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, pbonzini@...hat.com,
weijiang.yang@...el.com, rick.p.edgecombe@...el.com,
seanjc@...gle.com, x86@...nel.org, thomas.lendacky@....com,
bp@...en8.de
Subject: Re: [PATCH 8/9] KVM: SVM: Use KVM-governed features to track SHSTK
On Tue, 2023-10-10 at 20:02 +0000, John Allen wrote:
> Use the KVM-governed features framework to track whether SHSTK can be by
> both userspace and guest for SVM.
>
> Signed-off-by: John Allen <john.allen@....com>
> ---
> arch/x86/kvm/svm/svm.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/x86/kvm/svm/svm.c b/arch/x86/kvm/svm/svm.c
> index ee7c7d0a09ab..00a8cef3cbb8 100644
> --- a/arch/x86/kvm/svm/svm.c
> +++ b/arch/x86/kvm/svm/svm.c
> @@ -4366,6 +4366,7 @@ static void svm_vcpu_after_set_cpuid(struct kvm_vcpu *vcpu)
> kvm_governed_feature_check_and_set(vcpu, X86_FEATURE_PFTHRESHOLD);
> kvm_governed_feature_check_and_set(vcpu, X86_FEATURE_VGIF);
> kvm_governed_feature_check_and_set(vcpu, X86_FEATURE_VNMI);
> + kvm_governed_feature_check_and_set(vcpu, X86_FEATURE_SHSTK);
>
> svm_recalc_instruction_intercepts(vcpu, svm);
>
Reviewed-by: Maxim Levitsky <mlevitsk@...hat.com>
Best regards,
Maxim Levitsky
Powered by blists - more mailing lists