From: Kim Phillips <kim.phillips@amd.com>
To: <kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <x86@kernel.org>
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
Michael Roth <michael.roth@amd.com>,
Ashish Kalra <ashish.kalra@amd.com>,
"Nikunj A Dadhania" <nikunj@amd.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Sean Christopherson <seanjc@google.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kim Phillips <kim.phillips@amd.com>
Subject: [PATCH 0/2] KVM: SEV: Add support for the ALLOWED_SEV_FEATURES feature
Date: Thu, 1 Aug 2024 20:57:30 -0500 [thread overview]
Message-ID: <20240802015732.3192877-1-kim.phillips@amd.com> (raw)
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
next reply other threads:[~2024-08-02 1:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 1:57 Kim Phillips [this message]
2024-08-02 1:57 ` [PATCH 1/2] x86/cpufeatures: Add "Allowed SEV Features" Feature Kim Phillips
2024-08-07 16:06 ` Thomas Gleixner
2024-08-02 1:57 ` [PATCH 2/2] KVM: SEV: Configure "ALLOWED_SEV_FEATURES" VMCB Field Kim Phillips
2024-08-09 9:34 ` Nikunj A. Dadhania
2024-08-16 22:59 ` Sean Christopherson
2024-08-19 21:38 ` Kim Phillips
2024-08-19 22:23 ` Sean Christopherson
2024-08-20 15:26 ` Kim Phillips
2024-08-20 16:12 ` Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240802015732.3192877-1-kim.phillips@amd.com \
--to=kim.phillips@amd.com \
--cc=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=nikunj@amd.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome