diff options
| author | Tom Lendacky <thomas.lendacky@amd.com> | 2025-05-29 16:17:59 -0500 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2025-06-20 13:33:45 -0700 |
| commit | 9f4701e05faeec20350d9fc550e37ae8d2e08c88 (patch) | |
| tree | 803a4cd495bd5c4c3dcfd01b56f2bd81b980e04c /scripts/lib/kdoc/kdoc_parser.py | |
| parent | 28224ef02b56fceee2c161fe2a49a0bb197e44f5 (diff) | |
KVM: SVM: Allow SNP guest policy disallow running with SMT enabled
KVM currently returns -EINVAL when it attempts to create an SNP guest if
the SMT guest policy bit is not set. However, there is no reason to check
this, as there is no specific support in KVM that is required to support
this. The SEV firmware will determine if SMT has been enabled or disabled
in the BIOS and process the policy in the proper way:
- SMT enabled in BIOS
- Guest policy SMT == 0 ==> SNP_LAUNCH_START fails with POLICY_FAILURE
- Guest policy SMT == 1 ==> SNP_LAUNCH_START succeeds
- SMT disabled in BIOS
- Guest policy SMT == 0 ==> SNP_LAUNCH_START succeeds
- Guest policy SMT == 1 ==> SNP_LAUNCH_START succeeds
Remove the check for the SMT policy bit from snp_launch_start() and allow
the firmware to perform the proper checking.
Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
Link: https://lore.kernel.org/r/71043abdd9ef23b6f98fffa9c5c6045ac3a50187.1748553480.git.thomas.lendacky@amd.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_parser.py')
0 files changed, 0 insertions, 0 deletions