[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240802015732.3192877-1-kim.phillips@amd.com>
Date: Thu, 1 Aug 2024 20:57:30 -0500
From: Kim Phillips <kim.phillips@....com>
To: <kvm@...r.kernel.org>, <linux-kernel@...r.kernel.org>, <x86@...nel.org>
CC: Tom Lendacky <thomas.lendacky@....com>, Michael Roth
<michael.roth@....com>, Ashish Kalra <ashish.kalra@....com>, "Nikunj A
Dadhania" <nikunj@....com>, Borislav Petkov <bp@...en8.de>, Dave Hansen
<dave.hansen@...ux.intel.com>, Sean Christopherson <seanjc@...gle.com>,
"Paolo Bonzini" <pbonzini@...hat.com>, Ingo Molnar <mingo@...hat.com>, "H.
Peter Anvin" <hpa@...or.com>, Thomas Gleixner <tglx@...utronix.de>, Kim
Phillips <kim.phillips@....com>
Subject: [PATCH 0/2] KVM: SEV: Add support for the ALLOWED_SEV_FEATURES feature
AMD EPYC 5th generation processors have introduced a feature that allows
the hypervisor to control the SEV_FEATURES that are set for or by a
guest. The ALLOWED_SEV_FEATURES can be used by the hypervisor to enforce
that SEV-ES and SEV-SNP guests cannot enable features that the
hypervisor does not want to be enabled.
Patch 1 adds support to detect the feature.
Patch 2 configures the ALLOWED_SEV_FEATURES field in the VMCB
according to the features the hypervisor supports.
Based on tip/master commit a2767e7f31ad ("Merge branch into tip/master: 'x86/timers'")
Kishon Vijay Abraham I (2):
x86/cpufeatures: Add "Allowed SEV Features" Feature
KVM: SEV: Configure "ALLOWED_SEV_FEATURES" VMCB Field
arch/x86/include/asm/cpufeatures.h | 1 +
arch/x86/include/asm/svm.h | 6 +++++-
arch/x86/kvm/svm/sev.c | 5 +++++
3 files changed, 11 insertions(+), 1 deletion(-)
--
2.34.1
Powered by blists - more mailing lists