Basic SEV-SNP Selftests
Subsystems (7)
v6 cover Basic SEV-SNP Selftests
This patch series extends the sev_init2 and the sev_smoke test to exercise the SEV-SNP VM launch workflow.
Primarily, it introduces the architectural defines, its support in the SEV library and extends the tests to interact with the SEV-SNP ioctl() wrappers.
Patch 1 - Do not advertize SNP on incompatible firmware Patch 2 - Remove SEV support on platform init failure Patch 3 - SNP test for KVM_SEV_INIT2
Patch 4 - Add VMGEXIT helper
Patch 5 - Introduce SEV+ VM type check
Patch 6 - SNP iotcl() plumbing for the SEV library Patch 7 - Force set GUEST_MEMFD for SNP
Patch 8 - Cleanups of smoke test - Decouple policy from type Patch 9 - SNP smoke test
The series is based on
git.kernel.org/pub/scm/virt/kvm/kvm.git next
v5..v6
* Rename is_sev_platform_init to sev_fw_initialized (Nikunj)
* Rename KVM CPU feature X86_FEATURE_SNP to X86_FEATURE_SEV_SNP (Nikunj)
* Collected Tags from Nikunj, Pankaj, Srikanth.
v4..v5:
https://lore.kernel.org/kvm/[email protected]/
* Introduced a check to disable advertising support for SEV, SEV-ES and SNP when platform initialization fails (Nikunj)
* Remove the redundant SNP check within is_sev_vm() (Nikunj)
* Cleanup of the encrypt_region flow for better readability (Nikunj)
* Refactor paths to use the canonical $(ARCH) to rebase for kvm/next
v3..v4:
https://lore.kernel.org/kvm/[email protected]/
* Remove SNP FW API version check in the test and ensure the KVM capability advertizes the presence of the feature. Retain the minimum version definitions to exercise these API versions in the smoke test
* Retained only the SNP smoke test and SNP_INIT2 test
* The SNP architectural defined merged with SNP_INIT2 test patch
* SNP shutdown merged with SNP smoke test patch
* Add SEV VM type check to abstract comparisons and reduce clutter
* Define a SNP default policy which sets bits based on the presence of SMT
* Decouple privatization and encryption for it to be SNP agnostic
* Assert for only positive tests using vm_ioctl()
* Dropped tested-by tags
In summary - based on comments from Sean, I have primarily reduced the scope of this patch series to focus on breaking down the SNP smoke test patch (v3 - patch2) to first introduce SEV-SNP support and use this interface to extend the sev_init2 and the sev_smoke test.
The rest of the v3 patchset that introduces ioctl, pre fault, fallocate and negative tests, will be re-worked and re-introduced subsequently in future patch series post addressing the issues discussed.
v2..v3:
https://lore.kernel.org/kvm/[email protected]/
* Remove the assignments for the prefault and fallocate test type enums.
* Fix error message for sev launch measure and finish.
* Collect tested-by tags [Peter, Srikanth]
Pratik R. Sampat (9):
KVM: SEV: Disable SEV-SNP on FW validation failure
KVM: SEV: Disable SEV on platform init failure
KVM: selftests: SEV-SNP test for KVM_SEV_INIT2
KVM: selftests: Add VMGEXIT helper
KVM: selftests: Introduce SEV VM type check
KVM: selftests: Add library support for interacting with SNP
KVM: selftests: Force GUEST_MEMFD flag for SNP VM type
KVM: selftests: Abstractions for SEV to decouple policy from type
KVM: selftests: Add a basic SEV-SNP smoke test
arch/x86/kvm/svm/sev.c | 6 +- drivers/crypto/ccp/sev-dev.c | 16 +++ include/linux/psp-sev.h | 6 ++ .../selftests/kvm/include/x86/processor.h | 1 + tools/testing/selftests/kvm/include/x86/sev.h | 55 ++++++++++- tools/testing/selftests/kvm/lib/kvm_util.c | 7 +- .../testing/selftests/kvm/lib/x86/processor.c | 4 +- tools/testing/selftests/kvm/lib/x86/sev.c | 99 ++++++++++++++++++- .../selftests/kvm/x86/sev_init2_tests.c | 13 +++ .../selftests/kvm/x86/sev_smoke_test.c | 96 ++++++++++++++---- 10 files changed, 272 insertions(+), 31 deletions(-)
Signature · 1 line
2.43.0
PATCH v6 1/9 KVM: SEV: Disable SEV-SNP on FW validation failure
On incompatible firmware versions, SEV-SNP support is pulled and the setup is not performed. However, the platform and subsequently the KVM capability may continue to advertise support for it. Disable support for SEV-SNP if the FW version validation fails.
---
v5..v6:
* Collected tags from Nikunj and Srikanth.
--- arch/x86/kvm/svm/sev.c | 4 +++- drivers/crypto/ccp/sev-dev.c | 6 ++++++ include/linux/psp-sev.h | 3 +++ 3 files changed, 12 insertions(+), 1 deletion(-)
arch/x86/kvm/svm/sev.c +3 -1
@@ -3040,7 +3040,9 @@ void __init sev_hardware_setup(void) sev_es_asid_count = min_sev_asid -1 ;WARN_ON_ONCE (misc_cg_set_capacity (MISC_CG_RES_SEV_ES , sev_es_asid_count)); sev_es_supported = true; - sev_snp_supported = sev_snp_enabled &&cc_platform_has (CC_ATTR_HOST_SEV_SNP ); + sev_snp_supported = (sev_snp_enabled && +cc_platform_has (CC_ATTR_HOST_SEV_SNP ) && +snp_fw_valid ()); out:if (boot_cpu_has (X86_FEATURE_SEV ))
drivers/crypto/ccp/sev-dev.c +6 -0
@@ -122,6 +122,12 @@ static inline bool sev_version_greater_or_equal(u8 maj, u8 min)return false; } +bool snp_fw_valid (void ) +{ +return sev_version_greater_or_equal (SNP_MIN_API_MAJOR ,SNP_MIN_API_MINOR ); +} +EXPORT_SYMBOL_GPL (snp_fw_valid); +static void sev_irq_handler (int irq,void *data,unsigned int status) {struct sev_device *sev = data;
include/linux/psp-sev.h +3 -0
@@ -945,6 +945,7 @@ int sev_do_cmd(int cmd, void *data, int *psp_ret);void *psp_copy_user_blob (u64 uaddr,u32 len);void *snp_alloc_firmware_page (gfp_t mask);void snp_free_firmware_page (void *addr); +bool snp_fw_valid (void );#else /* !CONFIG_CRYPTO_DEV_SP_PSP */
@@ -979,6 +980,8 @@ static inline void *snp_alloc_firmware_page(gfp_t mask)static inline void snp_free_firmware_page (void *addr) { } +static inline bool snp_fw_valid (void ) {return false; } +#endif /* CONFIG_CRYPTO_DEV_SP_PSP */ #endif /* __PSP_SEV_H__ */
Signature · 1 line
2.43.0
Sean Christopherson
maintainerRe: [PATCH v6 1/9] KVM: SEV: Disable SEV-SNP on FW validation failure
Quoted 20 lines · Pratik R. Sampat
arch/x86/kvm/svm/sev.c +3
-1@@ -3040,7 +3040,9 @@ void __init sev_hardware_setup(void) sev_es_asid_count = min_sev_asid -1 ;WARN_ON_ONCE (misc_cg_set_capacity (MISC_CG_RES_SEV_ES , sev_es_asid_count)); sev_es_supported = true; - sev_snp_supported = sev_snp_enabled &&cc_platform_has (CC_ATTR_HOST_SEV_SNP ); + sev_snp_supported = (sev_snp_enabled && +cc_platform_has (CC_ATTR_HOST_SEV_SNP ) && +snp_fw_valid ()); out:if (boot_cpu_has (X86_FEATURE_SEV ))drivers/crypto/ccp/sev-dev.c +0
-0
drivers/crypto/ccp/sev-dev.c static inline bool sev_version_greater_or_equal(u8 maj, u8 min) · line 127
Quoted 6 lines
drivers/crypto/ccp/sev-dev.c +3
-0@@ -122,6 +122,12 @@ static inline bool sev_version_greater_or_equal(u8 maj, u8 min)return false; } +bool snp_fw_valid (void ) +{ +return sev_version_greater_or_equal (SNP_MIN_API_MAJOR ,SNP_MIN_API_MINOR );
This lacks any sense of abstraction. KVM doesn't care if the firmware is valid, KVM only cares if SNP is support. KVM _must_ run after ASP initialization[*], so I'm pretty sure KVM just needs a way to query sev->snp_initialized.
Re: [PATCH v6 1/9] KVM: SEV: Disable SEV-SNP on FW validation failure
Hello Sean,
Quoted 32 lines · Sean Christopherson
Quoted 20 lines · Pratik R. Sampat
arch/x86/kvm/svm/sev.c +3
-1@@ -3040,7 +3040,9 @@ void __init sev_hardware_setup(void) sev_es_asid_count = min_sev_asid -1 ;WARN_ON_ONCE (misc_cg_set_capacity (MISC_CG_RES_SEV_ES , sev_es_asid_count)); sev_es_supported = true; - sev_snp_supported = sev_snp_enabled &&cc_platform_has (CC_ATTR_HOST_SEV_SNP ); + sev_snp_supported = (sev_snp_enabled && +cc_platform_has (CC_ATTR_HOST_SEV_SNP ) && +snp_fw_valid ()); out:if (boot_cpu_has (X86_FEATURE_SEV ))drivers/crypto/ccp/sev-dev.c +0
-0drivers/crypto/ccp/sev-dev.c static inline bool sev_version_greater_or_equal(u8 maj, u8 min) · line 127
Quoted 6 lines
drivers/crypto/ccp/sev-dev.c +3
-0@@ -122,6 +122,12 @@ static inline bool sev_version_greater_or_equal(u8 maj, u8 min)return false; } +bool snp_fw_valid (void ) +{ +return sev_version_greater_or_equal (SNP_MIN_API_MAJOR ,SNP_MIN_API_MINOR );This lacks any sense of abstraction. KVM doesn't care if the firmware is valid, KVM only cares if SNP is support. KVM _must_ run after ASP initialization[*], so I'm pretty sure KVM just needs a way to query
sev->snp_initialized.
Quoted 1 line
Thank you for your reviews!
Sure, I can instead just export this function (with a better name) to return sev->snp_initialized within sev_hardware_setup().
PATCH v6 2/9 KVM: SEV: Disable SEV on platform init failure
In reply to Pratik R. SampatIf the platform initialization sev_platform_init() fails, SEV cannot be set up and a secure VM cannot be spawned. Therefore, in this case, ensure that KVM does not set up, nor advertise support for SEV, SEV-ES, and SEV-SNP.
---
v5..v6:
* Rename is_sev_platform_init to sev_fw_initialized (Nikunj)
* Collected tags from Srikanth.
--- arch/x86/kvm/svm/sev.c | 2 +- drivers/crypto/ccp/sev-dev.c | 10 ++++++++++ include/linux/psp-sev.h | 3 +++ 3 files changed, 14 insertions(+), 1 deletion(-)
arch/x86/kvm/svm/sev.c +1 -1
@@ -2957,7 +2957,7 @@ void __init sev_hardware_setup(void)bool sev_es_supported = false;bool sev_supported = false; -if (!sev_enabled || !npt_enabled || !nrips) +if (!sev_fw_initialized () || !sev_enabled || !npt_enabled || !nrips) goto out;/*
drivers/crypto/ccp/sev-dev.c +10 -0
@@ -81,6 +81,8 @@ MODULE_FIRMWARE("amd/amd_sev_fam19h_model1xh.sbin"); /* 4th gen EPYC */static bool psp_dead;static int psp_timeout; +static bool platform_init; +/* Trusted Memory Region (TMR): * The TMR is a 1MB area that must be 1MB aligned. Use the page allocator * to allocate the memory, which will return aligned memory for the specified
@@ -1358,6 +1360,12 @@ int sev_platform_init(struct sev_platform_init_args *args) }EXPORT_SYMBOL_GPL (sev_platform_init); +bool sev_fw_initialized (void ) +{ +return platform_init; +} +EXPORT_SYMBOL_GPL (sev_fw_initialized); +static int __sev_platform_shutdown_locked (int *error) {struct psp_device *psp = psp_master;
@@ -2427,6 +2435,8 @@ void sev_pci_init(void)if (rc)dev_err (sev->dev,"SEV: failed to INIT error %#x, rc %d\n" , args.error, rc); +else + platform_init = true;dev_info (sev->dev,"SEV%s API:%d.%d build:%d\n" , sev->snp_initialized ?"-SNP" :"" , sev->api_major, sev->api_minor, sev->build);
include/linux/psp-sev.h +3 -0
@@ -946,6 +946,7 @@ void *psp_copy_user_blob(u64 uaddr, u32 len);void *snp_alloc_firmware_page (gfp_t mask);void snp_free_firmware_page (void *addr);bool snp_fw_valid (void ); +bool sev_fw_initialized (void );#else /* !CONFIG_CRYPTO_DEV_SP_PSP */
@@ -982,6 +983,8 @@ static inline void snp_free_firmware_page(void *addr) { }static inline bool snp_fw_valid (void ) {return false; } +static inline bool sev_fw_initialized (void ) {return false; } +#endif /* CONFIG_CRYPTO_DEV_SP_PSP */ #endif /* __PSP_SEV_H__ */
Signature · 1 line
2.43.0
Sean Christopherson
maintainerRe: [PATCH v6 2/9] KVM: SEV: Disable SEV on platform init failure
Quoted 24 lines · Pratik R. Sampat
If the platform initialization
sev_platform_init()fails, SEV cannot be set up and a secure VM cannot be spawned. Therefore, in this case, ensure that KVM does not set up, nor advertise support for SEV, SEV-ES, and SEV-SNP.Suggested-by Nikunj A Dadhania <[email protected]>Tested-by Srikanth Aithal <[email protected]>Signed-off-by Pratik R. Sampat <[email protected]>---
v5..v6:* Rename
is_sev_platform_inittosev_fw_initialized(Nikunj)
* Collected tags from Srikanth.--- arch/x86/kvm/svm/sev.c | 2 +- drivers/crypto/ccp/sev-dev.c | 10 ++++++++++ include/linux/psp-sev.h | 3 +++ 3 files changed, 14 insertions(+), 1 deletion(-)arch/x86/kvm/svm/sev.c +0
-0
arch/x86/kvm/svm/sev.c void __init sev_hardware_setup(void) · line 2961
Quoted 6 lines
arch/x86/kvm/svm/sev.c +1
-1@@ -2957,7 +2957,7 @@ void __init sev_hardware_setup(void)bool sev_es_supported = false;bool sev_supported = false; -if (!sev_enabled || !npt_enabled || !nrips) +if (!sev_fw_initialized () || !sev_enabled || !npt_enabled || !nrips) goto out;
Me thinks this wasn't tested with KVM_AMD built-in[1]. I'm pretty sure Ashish's fix[2] solves all of this?
[1] https://lore.kernel.org/all/[email protected]
[2] https://lore.kernel.org/all/f78ddb64087df27e7bcb1ae0ab53f55aa0804fab.1739226950.git.ashish.kalra@amd.com
Re: [PATCH v6 2/9] KVM: SEV: Disable SEV on platform init failure
Quoted 35 lines · Sean Christopherson
Quoted 24 lines · Pratik R. Sampat
If the platform initialization
sev_platform_init()fails, SEV cannot be set up and a secure VM cannot be spawned. Therefore, in this case, ensure that KVM does not set up, nor advertise support for SEV, SEV-ES, and SEV-SNP.Suggested-by Nikunj A Dadhania <[email protected]>Tested-by Srikanth Aithal <[email protected]>Signed-off-by Pratik R. Sampat <[email protected]>---
v5..v6:* Rename
is_sev_platform_inittosev_fw_initialized(Nikunj)
* Collected tags from Srikanth.--- arch/x86/kvm/svm/sev.c | 2 +- drivers/crypto/ccp/sev-dev.c | 10 ++++++++++ include/linux/psp-sev.h | 3 +++ 3 files changed, 14 insertions(+), 1 deletion(-)arch/x86/kvm/svm/sev.c +0
-0arch/x86/kvm/svm/sev.c void __init sev_hardware_setup(void) · line 2961
Quoted 6 lines
arch/x86/kvm/svm/sev.c +1
-1@@ -2957,7 +2957,7 @@ void __init sev_hardware_setup(void)bool sev_es_supported = false;bool sev_supported = false; -if (!sev_enabled || !npt_enabled || !nrips) +if (!sev_fw_initialized () || !sev_enabled || !npt_enabled || !nrips) goto out;Me thinks this wasn't tested with
KVM_AMDbuilt-in[1]. I'm pretty sure Ashish's fix[2] solves all of this?
Quoted 2 lines
[1] https://lore.kernel.org/all/[email protected]
[2] https://lore.kernel.org/all/f78ddb64087df27e7bcb1ae0ab53f55aa0804fab.1739226950.git.ashish.kalra@amd.com
Thanks for pointing this out. I hadn't considered this earlier.
The combination of both of these should solve all of the issues caused by a failing SEV INIT. I will remove this patch for the next iteration then.
Thanks!
PATCH v6 3/9 KVM: selftests: SEV-SNP test for KVM_SEV_INIT2
In reply to Pratik R. SampatAdd the X86_FEATURE_SEV_SNP CPU feature to the architectural definition for the SEV-SNP VM type to exercise the KVM_SEV_INIT2 call. Ensure that the SNP test is skipped in scenarios where CPUID supports it but KVM does not, preventing reporting of failure in such cases.
---
v5..v6:
* Rename KVM CPU feature X86_FEATURE_SNP to X86_FEATURE_SEV_SNP (Nikunj)
* Collected tags from Nikunj and Srikanth.
--- tools/testing/selftests/kvm/include/x86/processor.h | 1 + tools/testing/selftests/kvm/x86/sev_init2_tests.c | 13 +++++++++++++ 2 files changed, 14 insertions(+)
tools/testing/selftests/kvm/include/x86/processor.h +1 -0
@@ -199,6 +199,7 @@ struct kvm_x86_cpu_feature {#define X86_FEATURE_VGIF KVM_X86_CPU_FEATURE(0x8000000A, 0, EDX, 16)#define X86_FEATURE_SEV KVM_X86_CPU_FEATURE(0x8000001F, 0, EAX, 1)#define X86_FEATURE_SEV_ES KVM_X86_CPU_FEATURE(0x8000001F, 0, EAX, 3) +#define X86_FEATURE_SEV_SNP KVM_X86_CPU_FEATURE(0x8000001F, 0, EAX, 4)/* * KVM defined paravirt features.
tools/testing/selftests/kvm/x86/sev_init2_tests.c +13 -0
@@ -28,6 +28,7 @@int kvm_fd;u64 supported_vmsa_features;bool have_sev_es; +bool have_snp;static int __sev_ioctl (int vm_fd,int cmd_id,void *data) {
@@ -83,6 +84,9 @@ void test_vm_types(void)if (have_sev_es)test_init2 (KVM_X86_SEV_ES_VM , &(struct kvm_sev_init ){}); +if (have_snp) +test_init2 (KVM_X86_SNP_VM , &(struct kvm_sev_init ){}); +test_init2_invalid (0 , &(struct kvm_sev_init ){},"VM type is KVM_X86_DEFAULT_VM" );if (kvm_check_cap (KVM_CAP_VM_TYPES ) &BIT (KVM_X86_SW_PROTECTED_VM ))
@@ -138,15 +142,24 @@ int main(int argc, char *argv[])"sev-es: KVM_CAP_VM_TYPES (%x) does not match cpuid (checking %x)" , kvm_check_cap(KVM_CAP_VM_TYPES), 1 << KVM_X86_SEV_ES_VM); + have_snp =kvm_check_cap (KVM_CAP_VM_TYPES ) &BIT (KVM_X86_SNP_VM ); +TEST_ASSERT (!have_snp ||kvm_cpu_has (X86_FEATURE_SEV_SNP ), +"sev-snp: KVM_CAP_VM_TYPES (%x) indicates SNP support (bit %d), but CPUID does not" , +kvm_check_cap (KVM_CAP_VM_TYPES ),KVM_X86_SNP_VM ); +test_vm_types ();test_flags (KVM_X86_SEV_VM );if (have_sev_es)test_flags (KVM_X86_SEV_ES_VM ); +if (have_snp) +test_flags (KVM_X86_SNP_VM );test_features (KVM_X86_SEV_VM ,0 );if (have_sev_es)test_features (KVM_X86_SEV_ES_VM , supported_vmsa_features); +if (have_snp) +test_features (KVM_X86_SNP_VM , supported_vmsa_features);return 0 ; }
Signature · 1 line
2.43.0
PATCH v6 4/9 KVM: selftests: Add VMGEXIT helper
In reply to Pratik R. SampatAbstract rep vmmcall coded into the VMGEXIT helper for the sev library.
No functional change intended.
---
v5..v6:
* Collected tags from Pankaj and Srikanth.
--- tools/testing/selftests/kvm/include/x86/sev.h | 2 ++ tools/testing/selftests/kvm/x86/sev_smoke_test.c | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-)
tools/testing/selftests/kvm/include/x86/sev.h +2 -0
@@ -27,6 +27,8 @@ enum sev_guest_state {#define GHCB_MSR_TERM_REQ 0x100 +#define VMGEXIT () { __asm__ __volatile__("rep; vmmcall"); } +void sev_vm_launch (struct kvm_vm *vm,uint32_t policy);void sev_vm_launch_measure (struct kvm_vm *vm,uint8_t *measurement);void sev_vm_launch_finish (struct kvm_vm *vm);
tools/testing/selftests/kvm/x86/sev_smoke_test.c +1 -1
@@ -27,7 +27,7 @@ static void guest_sev_es_code(void)* force "termination" to signal "done" via the GHCB MSR protocol. */ wrmsr (MSR_AMD64_SEV_ES_GHCB ,GHCB_MSR_TERM_REQ ); - __asm__ __volatile__("rep; vmmcall" ); +VMGEXIT (); }static void guest_sev_code (void )
Signature · 1 line
2.43.0
Sean Christopherson
maintainerRe: [PATCH v6 4/9] KVM: selftests: Add VMGEXIT helper
Quoted 22 lines · Pratik R. Sampat
Abstract rep vmmcall coded into the VMGEXIT helper for the sev library.
No functional change intended.
Reviewed-by Pankaj Gupta <[email protected]>Tested-by Srikanth Aithal <[email protected]>Signed-off-by Pratik R. Sampat <[email protected]>---
v5..v6:* Collected tags from Pankaj and Srikanth.
--- tools/testing/selftests/kvm/include/x86/sev.h | 2 ++ tools/testing/selftests/kvm/x86/sev_smoke_test.c | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-)tools/testing/selftests/kvm/include/x86/sev.h +0
-0
tools/testing/selftests/kvm/include/x86/sev.h enum sev_guest_state { · line 30
Quoted 4 lines
tools/testing/selftests/kvm/include/x86/sev.h +1
-0@@ -27,6 +27,8 @@ enum sev_guest_state {#define GHCB_MSR_TERM_REQ 0x100 +#define VMGEXIT () { __asm__ __volatile__("rep; vmmcall"); }
Please make this a proper inline function, there's no reason to use a macro.
Re: [PATCH v6 4/9] KVM: selftests: Add VMGEXIT helper
Quoted 24 lines · Sean Christopherson
Quoted 23 lines · Pratik R. Sampat
Abstract rep vmmcall coded into the VMGEXIT helper for the sev library.
No functional change intended.
Reviewed-by Pankaj Gupta <[email protected]>Tested-by Srikanth Aithal <[email protected]>Signed-off-by Pratik R. Sampat <[email protected]>---
v5..v6:* Collected tags from Pankaj and Srikanth.
--- tools/testing/selftests/kvm/include/x86/sev.h | 2 ++ tools/testing/selftests/kvm/x86/sev_smoke_test.c | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-)tools/testing/selftests/kvm/include/x86/sev.h +0
-0@@ -27,6 +27,8 @@ enum sev_guest_state {
Quoted 5 lines
tools/testing/selftests/kvm/include/x86/sev.h enum sev_guest_state { · line 30
Quoted 3 lines
tools/testing/selftests/kvm/include/x86/sev.h +1
-0#define GHCB_MSR_TERM_REQ 0x100 +#define VMGEXIT () { __asm__ __volatile__("rep; vmmcall"); }Please make this a proper inline function, there's no reason to use a macro.
Sure, I can make this an inline function.
PATCH v6 5/9 KVM: selftests: Introduce SEV VM type check
In reply to Pratik R. SampatIn preparation for SNP, declutter the vm type check by introducing a SEV-SNP VM type check as well as a transitive set of helper functions.
The SNP VM type is the subset of SEV-ES. Similarly, the SEV-ES and SNP types are subset of the SEV VM type check.
---
v5..v6:
* Commit message grammar
* Collected tags from Srikanth.
--- tools/testing/selftests/kvm/include/x86/sev.h | 4 ++++ tools/testing/selftests/kvm/lib/x86/processor.c | 4 ++-- tools/testing/selftests/kvm/lib/x86/sev.c | 17 +++++++++++++++++ .../testing/selftests/kvm/x86/sev_smoke_test.c | 2 +- 4 files changed, 24 insertions(+), 3 deletions(-)
tools/testing/selftests/kvm/include/x86/sev.h +4 -0
@@ -29,6 +29,10 @@ enum sev_guest_state {#define VMGEXIT () { __asm__ __volatile__("rep; vmmcall"); } +bool is_sev_vm (struct kvm_vm *vm); +bool is_sev_es_vm (struct kvm_vm *vm); +bool is_sev_snp_vm (struct kvm_vm *vm); +void sev_vm_launch (struct kvm_vm *vm,uint32_t policy);void sev_vm_launch_measure (struct kvm_vm *vm,uint8_t *measurement);void sev_vm_launch_finish (struct kvm_vm *vm);
tools/testing/selftests/kvm/lib/x86/processor.c +2 -2
@@ -639,7 +639,7 @@ void kvm_arch_vm_post_create(struct kvm_vm *vm)sync_global_to_guest (vm, host_cpu_is_amd);sync_global_to_guest (vm, is_forced_emulation_enabled); -if (vm->type ==KVM_X86_SEV_VM || vm->type ==KVM_X86_SEV_ES_VM ) { +if (is_sev_vm (vm)) {struct kvm_sev_init init = {0 };vm_sev_ioctl (vm,KVM_SEV_INIT2 , &init);
@@ -1156,7 +1156,7 @@ void kvm_get_cpu_address_width(unsigned int *pa_bits, unsigned int *va_bits)void kvm_init_vm_address_properties (struct kvm_vm *vm) { -if (vm->type ==KVM_X86_SEV_VM || vm->type ==KVM_X86_SEV_ES_VM ) { +if (is_sev_vm (vm)) { vm->arch.sev_fd =open_sev_dev_path_or_exit (); vm->arch.c_bit =BIT_ULL (this_cpu_property (X86_PROPERTY_SEV_C_BIT )); vm->gpa_tag_mask = vm->arch.c_bit;
tools/testing/selftests/kvm/lib/x86/sev.c +17 -0
@@ -4,6 +4,23 @@#include "sev.h" +bool is_sev_snp_vm (struct kvm_vm *vm) +{ +return vm->type ==KVM_X86_SNP_VM ; +} + +/* A SNP VM is also a SEV-ES VM */ +bool is_sev_es_vm (struct kvm_vm *vm) +{ +return is_sev_snp_vm (vm) || vm->type ==KVM_X86_SEV_ES_VM ; +} + +/* A SEV-ES and SNP VM is also a SEV VM */ +bool is_sev_vm (struct kvm_vm *vm) +{ +return is_sev_es_vm (vm) || vm->type ==KVM_X86_SEV_VM ; +} +/* * sparsebit_next_clear() can return 0 if [x, 2**64-1] are all set, and the * -1 would then cause an underflow back to 2**64 - 1. This is expected and
tools/testing/selftests/kvm/x86/sev_smoke_test.c +1 -1
@@ -123,7 +123,7 @@ static void test_sev(void *guest_code, uint64_t policy)for (;;) {vcpu_run (vcpu); -if (policy &SEV_POLICY_ES ) { +if (is_sev_es_vm (vm)) {TEST_ASSERT (vcpu->run->exit_reason ==KVM_EXIT_SYSTEM_EVENT ,"Wanted SYSTEM_EVENT, got %s" ,exit_reason_str (vcpu->run->exit_reason));
Signature · 1 line
2.43.0
PATCH v6 6/9 KVM: selftests: Add library support for interacting with SNP
In reply to Pratik R. SampatExtend the SEV library to include support for SNP ioctl() wrappers, which aid in launching and interacting with a SEV-SNP guest.
---
v5..v6:
* Collected tags from Srikanth.
--- tools/testing/selftests/kvm/include/x86/sev.h | 49 ++++++++++- tools/testing/selftests/kvm/lib/x86/sev.c | 82 +++++++++++++++++-- 2 files changed, 125 insertions(+), 6 deletions(-)
tools/testing/selftests/kvm/include/x86/sev.h +48 -1
@@ -22,9 +22,20 @@ enum sev_guest_state { SEV_GUEST_STATE_RUNNING, }; +/* Minimum firmware version required for the SEV-SNP support */ +#define SNP_MIN_API_MAJOR 1 +#define SNP_MIN_API_MINOR 51 +#define SEV_POLICY_NO_DBG (1UL << 0)#define SEV_POLICY_ES (1UL << 2) +#define SNP_POLICY_SMT (1ULL << 16) +#define SNP_POLICY_RSVD_MBO (1ULL << 17) +#define SNP_POLICY_DBG (1ULL << 19) + +#define SNP_FW_VER_MINOR (min) ((uint8_t)(min) << 0) +#define SNP_FW_VER_MAJOR (maj) ((uint8_t)(maj) << 8) +#define GHCB_MSR_TERM_REQ 0x100#define VMGEXIT () { __asm__ __volatile__("rep; vmmcall"); }
@@ -36,13 +47,35 @@ bool is_sev_snp_vm(struct kvm_vm *vm);void sev_vm_launch (struct kvm_vm *vm,uint32_t policy);void sev_vm_launch_measure (struct kvm_vm *vm,uint8_t *measurement);void sev_vm_launch_finish (struct kvm_vm *vm); +void snp_vm_launch_start (struct kvm_vm *vm,uint64_t policy); +void snp_vm_launch_update (struct kvm_vm *vm); +void snp_vm_launch_finish (struct kvm_vm *vm);struct kvm_vm *vm_sev_create_with_one_vcpu (uint32_t type,void *guest_code,struct kvm_vcpu **cpu); -void vm_sev_launch (struct kvm_vm *vm,uint32_t policy,uint8_t *measurement); +void vm_sev_launch (struct kvm_vm *vm,uint64_t policy,uint8_t *measurement);kvm_static_assert (SEV_RET_SUCCESS ==0 ); +/* +* A SEV-SNP VM requires the policy reserved bit to always be set. +* The SMT policy bit is also required to be set based on SMT being +* available and active on the system. +*/ +static inline u64 snp_default_policy (void ) +{ +bool smt_active = false; +FILE *f; + + f =fopen ("/sys/devices/system/cpu/smt/active" ,"r" ); +if (f) { + smt_active =fgetc (f) -'0' ; +fclose (f); + } + +return SNP_POLICY_RSVD_MBO | (smt_active ?SNP_POLICY_SMT :0 ); +} +/* * The KVM_MEMORY_ENCRYPT_OP uAPI is utter garbage and takes an "unsigned long" * instead of a proper struct. The size of the parameter is embedded in the
@@ -76,6 +109,7 @@ kvm_static_assert(SEV_RET_SUCCESS == 0);void sev_vm_init (struct kvm_vm *vm);void sev_es_vm_init (struct kvm_vm *vm); +void snp_vm_init (struct kvm_vm *vm);static inline void sev_register_encrypted_memory (struct kvm_vm *vm,struct userspace_mem_region *region)
@@ -99,4 +133,17 @@ static inline void sev_launch_update_data(struct kvm_vm *vm, vm_paddr_t gpa, vm_sev_ioctl(vm, KVM_SEV_LAUNCH_UPDATE_DATA, &update_data); } +static inline void snp_launch_update_data (struct kvm_vm *vm,vm_paddr_t gpa, +uint64_t hva,uint64_t size,uint8_t type) +{ +struct kvm_sev_snp_launch_update update_data = { + .uaddr = hva, + .gfn_start = gpa >>PAGE_SHIFT , + .len = size, + .type = type, + }; + +vm_sev_ioctl (vm,KVM_SEV_SNP_LAUNCH_UPDATE , &update_data); +} +#endif /* SELFTEST_KVM_SEV_H */
tools/testing/selftests/kvm/lib/x86/sev.c +77 -5
124 lines not on this page · raw message
Signature · 1 line
2.43.0
Sean Christopherson
maintainerRe: [PATCH v6 6/9] KVM: selftests: Add library support for interacting with SNP
Quoted 19 lines · Pratik R. Sampat
Extend the SEV library to include support for SNP
ioctl()wrappers, which aid in launching and interacting with a SEV-SNP guest.Tested-by Srikanth Aithal <[email protected]>Signed-off-by Pratik R. Sampat <[email protected]>---
v5..v6:* Collected tags from Srikanth.
--- tools/testing/selftests/kvm/include/x86/sev.h | 49 ++++++++++- tools/testing/selftests/kvm/lib/x86/sev.c | 82 +++++++++++++++++-- 2 files changed, 125 insertions(+), 6 deletions(-)tools/testing/selftests/kvm/include/x86/sev.h +0
-0
tools/testing/selftests/kvm/include/x86/sev.h enum sev_guest_state { · line 27
Quoted 6 lines
tools/testing/selftests/kvm/include/x86/sev.h +3
-0@@ -22,9 +22,20 @@ enum sev_guest_state { SEV_GUEST_STATE_RUNNING, }; +/* Minimum firmware version required for the SEV-SNP support */ +#define SNP_MIN_API_MAJOR 1 +#define SNP_MIN_API_MINOR 51
Dead code. Selftests don't care about this.
tools/testing/selftests/kvm/include/x86/sev.h enum sev_guest_state { · line 37
Quoted 9 lines
tools/testing/selftests/kvm/include/x86/sev.h +6
-0#define SEV_POLICY_NO_DBG (1UL << 0)#define SEV_POLICY_ES (1UL << 2) +#define SNP_POLICY_SMT (1ULL << 16) +#define SNP_POLICY_RSVD_MBO (1ULL << 17) +#define SNP_POLICY_DBG (1ULL << 19) + +#define SNP_FW_VER_MINOR (min) ((uint8_t)(min) << 0) +#define SNP_FW_VER_MAJOR (maj) ((uint8_t)(maj) << 8)
Also dead code.
Quoted 19 lines
tools/testing/selftests/kvm/include/x86/sev.h +5
-1#define GHCB_MSR_TERM_REQ 0x100#define VMGEXIT () { __asm__ __volatile__("rep; vmmcall"); }@@ -36,13 +47,35 @@ bool is_sev_snp_vm(struct kvm_vm *vm);void sev_vm_launch (struct kvm_vm *vm,uint32_t policy);void sev_vm_launch_measure (struct kvm_vm *vm,uint8_t *measurement);void sev_vm_launch_finish (struct kvm_vm *vm); +void snp_vm_launch_start (struct kvm_vm *vm,uint64_t policy); +void snp_vm_launch_update (struct kvm_vm *vm); +void snp_vm_launch_finish (struct kvm_vm *vm);struct kvm_vm *vm_sev_create_with_one_vcpu (uint32_t type,void *guest_code,struct kvm_vcpu **cpu); -void vm_sev_launch (struct kvm_vm *vm,uint32_t policy,uint8_t *measurement); +void vm_sev_launch (struct kvm_vm *vm,uint64_t policy,uint8_t *measurement);kvm_static_assert (SEV_RET_SUCCESS ==0 ); +/*
tools/testing/selftests/kvm/include/x86/sev.h bool is_sev_snp_vm(struct kvm_vm *vm); · line 70
Quoted 10 lines
tools/testing/selftests/kvm/include/x86/sev.h +10
-0+* A SEV-SNP VM requires the policy reserved bit to always be set. +* The SMT policy bit is also required to be set based on SMT being +* available and active on the system. +*/ +static inline u64 snp_default_policy (void ) +{ +bool smt_active = false; +FILE *f; + + f =fopen ("/sys/devices/system/cpu/smt/active" ,"r" );
Please add a helper to query if SMT is enabled. I doubt there will ever be many users of this, but it doesn't seem like something that should buried in SNP code.
Ha! smt_possible() in tools/testing/selftests/kvm/x86/hyperv_cpuid.c is already guilty of burying a related helper, and it looks like it's a more robust version.
Quoted 55 lines
tools/testing/selftests/kvm/include/x86/sev.h +22
-0+if (f) { + smt_active =fgetc (f) -'0' ; +fclose (f); + } + +return SNP_POLICY_RSVD_MBO | (smt_active ?SNP_POLICY_SMT :0 ); +} +/* * The KVM_MEMORY_ENCRYPT_OP uAPI is utter garbage and takes an "unsigned long" * instead of a proper struct. The size of the parameter is embedded in the @@ -76,6 +109,7 @@ kvm_static_assert(SEV_RET_SUCCESS == 0);void sev_vm_init (struct kvm_vm *vm);void sev_es_vm_init (struct kvm_vm *vm); +void snp_vm_init (struct kvm_vm *vm);static inline void sev_register_encrypted_memory (struct kvm_vm *vm,struct userspace_mem_region *region)@@ -99,4 +133,17 @@ static inline void sev_launch_update_data(struct kvm_vm *vm, vm_paddr_t gpa, vm_sev_ioctl(vm, KVM_SEV_LAUNCH_UPDATE_DATA, &update_data); } +static inline void snp_launch_update_data (struct kvm_vm *vm,vm_paddr_t gpa, +uint64_t hva,uint64_t size,uint8_t type) +{ +struct kvm_sev_snp_launch_update update_data = { + .uaddr = hva, + .gfn_start = gpa >>PAGE_SHIFT , + .len = size, + .type = type, + }; + +vm_sev_ioctl (vm,KVM_SEV_SNP_LAUNCH_UPDATE , &update_data); +} +#endif /* SELFTEST_KVM_SEV_H */ tools/testing/selftests/kvm/lib/x86/sev.c +2
-1@@ -31,7 +31,8 @@ bool is_sev_vm(struct kvm_vm *vm)* and find the first range, but that's correct because the condition * expression would cause us to quit the loop. */ -static void encrypt_region (struct kvm_vm *vm,struct userspace_mem_region *region) +static void encrypt_region (struct kvm_vm *vm,struct userspace_mem_region *region, +uint8_t page_type) {const struct sparsebit *protected_phy_pages = region->protected_phy_pages;const vm_paddr_t gpa_base = region->region.guest_phys_addr;@@ -41,13 +42,35 @@ static void encrypt_region(struct kvm_vm *vm, struct userspace_mem_region *regioif (!sparsebit_any_set (protected_phy_pages))return ;
tools/testing/selftests/kvm/lib/x86/sev.c static void encrypt_region(struct kvm_vm *vm, struct userspace_mem_region *regio · line 52
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86/sev.c +3
-2-sev_register_encrypted_memory (vm, region); +if (!is_sev_snp_vm (vm)) +sev_register_encrypted_memory (vm, region);sparsebit_for_each_set_range (protected_phy_pages, i, j) {const uint64_t size = (j - i +1 ) * vm->page_size;const uint64_t offset = (i - lowest_page_in_region) * vm->page_size; -sev_launch_update_data (vm, gpa_base + offset, size); +if (is_sev_snp_vm (vm)) {
Curly braces are unnecessary.
tools/testing/selftests/kvm/lib/x86/sev.c static void encrypt_region(struct kvm_vm *vm, struct userspace_mem_region *regio · line 62
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86/sev.c +10
-0+snp_launch_update_data (vm, gpa_base + offset, + (uint64_t )addr_gpa2hva (vm, gpa_base + offset), + size, page_type); + }else { +sev_launch_update_data (vm, gpa_base + offset, size); + } + } +} + +static void privatize_region (struct kvm_vm *vm,struct userspace_mem_region *region)
Can't this just be a param to encrypt_region() that also says "make it private"?
Quoted 15 lines
tools/testing/selftests/kvm/lib/x86/sev.c +11
-0+{ +const struct sparsebit *protected_phy_pages = region->protected_phy_pages; +const vm_paddr_t gpa_base = region->region.guest_phys_addr; +const sparsebit_idx_t lowest_page_in_region = gpa_base >> vm->page_shift; +sparsebit_idx_t i, j; + +sparsebit_for_each_set_range (protected_phy_pages, i, j) { +const uint64_t size = (j - i +1 ) * vm->page_size; +const uint64_t offset = (i - lowest_page_in_region) * vm->page_size; + +vm_mem_set_private (vm, gpa_base + offset, size); } }
tools/testing/selftests/kvm/lib/x86/sev.c void sev_es_vm_init(struct kvm_vm *vm) · line 107
Quoted 8 lines
tools/testing/selftests/kvm/lib/x86/sev.c +5
-0@@ -77,6 +100,14 @@ void sev_es_vm_init(struct kvm_vm *vm) } } +void snp_vm_init (struct kvm_vm *vm) +{ +struct kvm_sev_init init = {0 }; + +assert (vm->type ==KVM_X86_SNP_VM );
Use TEST_ASSERT(), or do nothing, don't use assert().
tools/testing/selftests/kvm/lib/x86/sev.c void sev_vm_launch(struct kvm_vm *vm, uint32_t policy) · line 127
Quoted 12 lines
tools/testing/selftests/kvm/lib/x86/sev.c +4
-1+vm_sev_ioctl (vm,KVM_SEV_INIT2 , &init); +} +void sev_vm_launch (struct kvm_vm *vm,uint32_t policy) {struct kvm_sev_launch_start launch_start = {@@ -93,7 +124,7 @@ void sev_vm_launch(struct kvm_vm *vm, uint32_t policy)TEST_ASSERT_EQ (status.state,SEV_GUEST_STATE_LAUNCH_UPDATE );hash_for_each (vm->regions.slot_hash, ctr, region, slot_node) -encrypt_region (vm, region); +encrypt_region (vm, region,0 );
Please add an enum/macro instead of open coding a literal '0'. I gotta assume there's an appropriate name for page type '0'.
Quoted 3 lines
tools/testing/selftests/kvm/lib/x86/sev.c +0
-0if (policy &SEV_POLICY_ES )vm_sev_ioctl (vm,KVM_SEV_LAUNCH_UPDATE_VMSA ,NULL );
Re: [PATCH v6 6/9] KVM: selftests: Add library support for interacting with SNP
Quoted 6 lines · Sean Christopherson
Quoted 5 lines · Pratik R. Sampat
Extend the SEV library to include support for SNP
ioctl()wrappers, which aid in launching and interacting with a SEV-SNP guest.Tested-by Srikanth Aithal <[email protected]>Signed-off-by Pratik R. Sampat <[email protected]>
[..snip..]
Quoted 15 lines
tools/testing/selftests/kvm/include/x86/sev.h bool is_sev_snp_vm(struct kvm_vm *vm); · line 70
Quoted 11 lines
tools/testing/selftests/kvm/include/x86/sev.h +11
-0+/* +* A SEV-SNP VM requires the policy reserved bit to always be set. +* The SMT policy bit is also required to be set based on SMT being +* available and active on the system. +*/ +static inline u64 snp_default_policy (void ) +{ +bool smt_active = false; +FILE *f; + + f =fopen ("/sys/devices/system/cpu/smt/active" ,"r" );Please add a helper to query if SMT is enabled. I doubt there will ever be many users of this, but it doesn't seem like something that should buried in SNP code.
Quoted 3 lines
Ha!
smt_possible()intools/testing/selftests/kvm/x86/hyperv_cpuid.cis already guilty of burying a related helper, and it looks like it's a more robust version.
You're right, a more general helper is in order here.
Since the hyperv_cpuid selftest only seems to care about whether SMT is possible (i.e., it may or may not be enabled) and we care about it being enabled as well, for the flag to be set. I should make a more generic variant(s) that can be accessible to both. Maybe I can implement it within testing/selftests/kvm/include/x86_processor.h?
Quoted 59 lines
Quoted 59 lines
tools/testing/selftests/kvm/include/x86/sev.h +22
-0+if (f) { + smt_active =fgetc (f) -'0' ; +fclose (f); + } + +return SNP_POLICY_RSVD_MBO | (smt_active ?SNP_POLICY_SMT :0 ); +} +/* * The KVM_MEMORY_ENCRYPT_OP uAPI is utter garbage and takes an "unsigned long" * instead of a proper struct. The size of the parameter is embedded in the @@ -76,6 +109,7 @@ kvm_static_assert(SEV_RET_SUCCESS == 0);void sev_vm_init (struct kvm_vm *vm);void sev_es_vm_init (struct kvm_vm *vm); +void snp_vm_init (struct kvm_vm *vm);static inline void sev_register_encrypted_memory (struct kvm_vm *vm,struct userspace_mem_region *region)@@ -99,4 +133,17 @@ static inline void sev_launch_update_data(struct kvm_vm *vm, vm_paddr_t gpa, vm_sev_ioctl(vm, KVM_SEV_LAUNCH_UPDATE_DATA, &update_data); } +static inline void snp_launch_update_data (struct kvm_vm *vm,vm_paddr_t gpa, +uint64_t hva,uint64_t size,uint8_t type) +{ +struct kvm_sev_snp_launch_update update_data = { + .uaddr = hva, + .gfn_start = gpa >>PAGE_SHIFT , + .len = size, + .type = type, + }; + +vm_sev_ioctl (vm,KVM_SEV_SNP_LAUNCH_UPDATE , &update_data); +} +#endif /* SELFTEST_KVM_SEV_H */ tools/testing/selftests/kvm/lib/x86/sev.c +4
-2@@ -31,7 +31,8 @@ bool is_sev_vm(struct kvm_vm *vm)* and find the first range, but that's correct because the condition * expression would cause us to quit the loop. */ -static void encrypt_region (struct kvm_vm *vm,struct userspace_mem_region *region) +static void encrypt_region (struct kvm_vm *vm,struct userspace_mem_region *region, +uint8_t page_type) {const struct sparsebit *protected_phy_pages = region->protected_phy_pages;const vm_paddr_t gpa_base = region->region.guest_phys_addr;@@ -41,13 +42,35 @@ static void encrypt_region(struct kvm_vm *vm, struct userspace_mem_region *regioif (!sparsebit_any_set (protected_phy_pages))return ; -sev_register_encrypted_memory (vm, region); +if (!is_sev_snp_vm (vm)) +sev_register_encrypted_memory (vm, region);
Quoted 8 lines
tools/testing/selftests/kvm/lib/x86/sev.c static void encrypt_region(struct kvm_vm *vm, struct userspace_mem_region *regio · line 52
Quoted 6 lines
tools/testing/selftests/kvm/lib/x86/sev.c +1
-1sparsebit_for_each_set_range (protected_phy_pages, i, j) {const uint64_t size = (j - i +1 ) * vm->page_size;const uint64_t offset = (i - lowest_page_in_region) * vm->page_size; -sev_launch_update_data (vm, gpa_base + offset, size); +if (is_sev_snp_vm (vm)) {Curly braces are unnecessary.
Ack. Will be remove them.
Quoted 14 lines
tools/testing/selftests/kvm/lib/x86/sev.c static void encrypt_region(struct kvm_vm *vm, struct userspace_mem_region *regio · line 62
Quoted 11 lines
tools/testing/selftests/kvm/lib/x86/sev.c +10
-0+snp_launch_update_data (vm, gpa_base + offset, + (uint64_t )addr_gpa2hva (vm, gpa_base + offset), + size, page_type); + }else { +sev_launch_update_data (vm, gpa_base + offset, size); + } + } +} + +static void privatize_region (struct kvm_vm *vm,struct userspace_mem_region *region)Can't this just be a param to
encrypt_region()that also says "make it private"?
Sure, I can parameterize encrypt_region() to have a private boolean. The idea was essentially to ensure that privatizing and encryption can be called separately if they wanted to. However, since this is currently only used in tandem (by SNP) I can remove this to reduce duplication.
Quoted 18 lines
Quoted 18 lines
tools/testing/selftests/kvm/lib/x86/sev.c +11
-0+{ +const struct sparsebit *protected_phy_pages = region->protected_phy_pages; +const vm_paddr_t gpa_base = region->region.guest_phys_addr; +const sparsebit_idx_t lowest_page_in_region = gpa_base >> vm->page_shift; +sparsebit_idx_t i, j; + +sparsebit_for_each_set_range (protected_phy_pages, i, j) { +const uint64_t size = (j - i +1 ) * vm->page_size; +const uint64_t offset = (i - lowest_page_in_region) * vm->page_size; + +vm_mem_set_private (vm, gpa_base + offset, size); } }@@ -77,6 +100,14 @@ void sev_es_vm_init(struct kvm_vm *vm) } }
Quoted 8 lines
tools/testing/selftests/kvm/lib/x86/sev.c void sev_es_vm_init(struct kvm_vm *vm) · line 107
Quoted 5 lines
tools/testing/selftests/kvm/lib/x86/sev.c +5
-0+void snp_vm_init (struct kvm_vm *vm) +{ +struct kvm_sev_init init = {0 }; + +assert (vm->type ==KVM_X86_SNP_VM );Use
TEST_ASSERT(), or do nothing, don't useassert().
Alright, I can do that.
I will also send another cleanups patch to remove asserts() in the SEV, SEV-ES counterparts too in that case!
Quoted 9 lines
Quoted 9 lines
tools/testing/selftests/kvm/lib/x86/sev.c +3
-0+vm_sev_ioctl (vm,KVM_SEV_INIT2 , &init); +} +void sev_vm_launch (struct kvm_vm *vm,uint32_t policy) {struct kvm_sev_launch_start launch_start = {@@ -93,7 +124,7 @@ void sev_vm_launch(struct kvm_vm *vm, uint32_t policy)TEST_ASSERT_EQ (status.state,SEV_GUEST_STATE_LAUNCH_UPDATE );
Quoted 7 lines
tools/testing/selftests/kvm/lib/x86/sev.c void sev_vm_launch(struct kvm_vm *vm, uint32_t policy) · line 127
Quoted 3 lines
tools/testing/selftests/kvm/lib/x86/sev.c +1
-1hash_for_each (vm->regions.slot_hash, ctr, region, slot_node) -encrypt_region (vm, region); +encrypt_region (vm, region,0 );Please add an enum/macro instead of open coding a literal '0'. I gotta assume there's an appropriate name for page type '0'.
For SNP, we supply this parameter to determine the page type for SNP launch update defined as KVM_SEV_SNP_PAGE_TYPE_*. For SEV/SEV-ES, however, the page type doesn't really get factored in and falls through unaccounted in that case, so I had passed a zero to it.
Having said that, having a literal here is quite unclean. Maybe I can pass one of the existing page types to it or, better yet, define a new KVM_SEV_PAGE_TYPE_[RESERVED|UNUSED] type instead for our selftest header?
Quoted 3 lines
Quoted 3 lines
tools/testing/selftests/kvm/lib/x86/sev.c +0
-0if (policy &SEV_POLICY_ES )vm_sev_ioctl (vm,KVM_SEV_LAUNCH_UPDATE_VMSA ,NULL );
Sean Christopherson
maintainerRe: [PATCH v6 6/9] KVM: selftests: Add library support for interacting with SNP
Quoted 29 lines · Pratik Rajesh Sampat
Quoted 6 lines · Sean Christopherson
Quoted 5 lines · Pratik R. Sampat
Extend the SEV library to include support for SNP
ioctl()wrappers, which aid in launching and interacting with a SEV-SNP guest.Tested-by Srikanth Aithal <[email protected]>Signed-off-by Pratik R. Sampat <[email protected]>[..snip..]
Quoted 15 lines
tools/testing/selftests/kvm/include/x86/sev.h bool is_sev_snp_vm(struct kvm_vm *vm); · line 70
Quoted 11 lines
tools/testing/selftests/kvm/include/x86/sev.h +11
-0+/* +* A SEV-SNP VM requires the policy reserved bit to always be set. +* The SMT policy bit is also required to be set based on SMT being +* available and active on the system. +*/ +static inline u64 snp_default_policy (void ) +{ +bool smt_active = false; +FILE *f; + + f =fopen ("/sys/devices/system/cpu/smt/active" ,"r" );Please add a helper to query if SMT is enabled. I doubt there will ever be many users of this, but it doesn't seem like something that should buried in SNP code.
Quoted 3 lines
Ha!
smt_possible()intools/testing/selftests/kvm/x86/hyperv_cpuid.cis already guilty of burying a related helper, and it looks like it's a more robust version.
Quoted 7 lines
You're right, a more general helper is in order here.
Since the
hyperv_cpuidselftest only seems to care about whether SMT is possible (i.e., it may or may not be enabled) and we care about it being enabled as well, for the flag to be set. I should make a more generic variant(s) that can be accessible to both. Maybe I can implement it withintesting/selftests/kvm/include/x86_processor.h?
It should go in kvm_util.h, /sys/devices/system/cpu/smt/active is a generic interface provided by kernel/cpu.c.
Quoted 16 lines
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86/sev.c void sev_vm_launch(struct kvm_vm *vm, uint32_t policy) · line 127
Quoted 6 lines
tools/testing/selftests/kvm/lib/x86/sev.c +1
-1@@ -93,7 +124,7 @@ void sev_vm_launch(struct kvm_vm *vm, uint32_t policy)TEST_ASSERT_EQ (status.state,SEV_GUEST_STATE_LAUNCH_UPDATE );hash_for_each (vm->regions.slot_hash, ctr, region, slot_node) -encrypt_region (vm, region); +encrypt_region (vm, region,0 );Please add an enum/macro instead of open coding a literal '0'. I gotta assume there's an appropriate name for page type '0'.
For SNP, we supply this parameter to determine the page type for SNP launch update defined as KVM_SEV_SNP_PAGE_TYPE_*. For SEV/SEV-ES, however, the page type doesn't really get factored in and falls through unaccounted in that case, so I had passed a zero to it.
Quoted 4 lines
Having said that, having a literal here is quite unclean. Maybe I can pass one of the existing page types to it or, better yet, define a new KVM_SEV_PAGE_TYPE_[RESERVED|UNUSED] type instead for our selftest header?
Ya, define something new and arbitrary. I vote for either KVM_SEV_PAGE_TYPE_NONE or KVM_SEV_PAGE_TYPE_INVALID. RESERVED suggests the page is "valid" but reserved for some entity. Ditto for UNUSED; valid, but not yet claimed.
Re: [PATCH v6 6/9] KVM: selftests: Add library support for interacting with SNP
Quoted 32 lines · Sean Christopherson
Quoted 31 lines · Pratik Rajesh Sampat
Quoted 6 lines · Sean Christopherson
Quoted 5 lines · Pratik R. Sampat
Extend the SEV library to include support for SNP
ioctl()wrappers, which aid in launching and interacting with a SEV-SNP guest.Tested-by Srikanth Aithal <[email protected]>Signed-off-by Pratik R. Sampat <[email protected]>[..snip..]
Quoted 15 lines
tools/testing/selftests/kvm/include/x86/sev.h bool is_sev_snp_vm(struct kvm_vm *vm); · line 70
Quoted 11 lines
tools/testing/selftests/kvm/include/x86/sev.h +11
-0+/* +* A SEV-SNP VM requires the policy reserved bit to always be set. +* The SMT policy bit is also required to be set based on SMT being +* available and active on the system. +*/ +static inline u64 snp_default_policy (void ) +{ +bool smt_active = false; +FILE *f; + + f =fopen ("/sys/devices/system/cpu/smt/active" ,"r" );Please add a helper to query if SMT is enabled. I doubt there will ever be many users of this, but it doesn't seem like something that should buried in SNP code.
Quoted 3 lines
Ha!
smt_possible()intools/testing/selftests/kvm/x86/hyperv_cpuid.cis already guilty of burying a related helper, and it looks like it's a more robust version.You're right, a more general helper is in order here.
Quoted 9 lines
Quoted 5 lines
Since the
hyperv_cpuidselftest only seems to care about whether SMT is possible (i.e., it may or may not be enabled) and we care about it being enabled as well, for the flag to be set. I should make a more generic variant(s) that can be accessible to both. Maybe I can implement it withintesting/selftests/kvm/include/x86_processor.h?It should go in
kvm_util.h,/sys/devices/system/cpu/smt/activeis a generic interface provided bykernel/cpu.c.
Sure, I will move it to the kvm_util header.
Quoted 16 lines
Quoted 16 lines
Quoted 10 lines
tools/testing/selftests/kvm/lib/x86/sev.c void sev_vm_launch(struct kvm_vm *vm, uint32_t policy) · line 127
Quoted 6 lines
tools/testing/selftests/kvm/lib/x86/sev.c +1
-1@@ -93,7 +124,7 @@ void sev_vm_launch(struct kvm_vm *vm, uint32_t policy)TEST_ASSERT_EQ (status.state,SEV_GUEST_STATE_LAUNCH_UPDATE );hash_for_each (vm->regions.slot_hash, ctr, region, slot_node) -encrypt_region (vm, region); +encrypt_region (vm, region,0 );Please add an enum/macro instead of open coding a literal '0'. I gotta assume there's an appropriate name for page type '0'.
For SNP, we supply this parameter to determine the page type for SNP launch update defined as KVM_SEV_SNP_PAGE_TYPE_*. For SEV/SEV-ES, however, the page type doesn't really get factored in and falls through unaccounted in that case, so I had passed a zero to it.
Quoted 8 lines
Quoted 4 lines
Having said that, having a literal here is quite unclean. Maybe I can pass one of the existing page types to it or, better yet, define a new KVM_SEV_PAGE_TYPE_[RESERVED|UNUSED] type instead for our selftest header?
Ya, define something new and arbitrary. I vote for either
KVM_SEV_PAGE_TYPE_NONEorKVM_SEV_PAGE_TYPE_INVALID. RESERVED suggests the page is "valid" but reserved for some entity. Ditto for UNUSED; valid, but not yet claimed.
Got it.
Thank you!
PATCH v6 7/9 KVM: selftests: Force GUEST_MEMFD flag for SNP VM type
In reply to Pratik R. SampatForce the SEV-SNP VM type to set the KVM_MEM_GUEST_MEMFD flag for the creation of private memslots.
---
v5..v6:
* Collected tags from Srikanth.
--- tools/testing/selftests/kvm/lib/kvm_util.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
tools/testing/selftests/kvm/lib/kvm_util.c +5 -2
@@ -413,14 +413,17 @@ struct kvm_vm *__vm_create(struct vm_shape shape, uint32_t nr_runnable_vcpus, nr_extra_pages);struct userspace_mem_region *slot0;struct kvm_vm *vm; -int i; +int i, flags =0 ;pr_debug ("%s: mode='%s' type='%d', pages='%ld'\n" , __func__,vm_guest_mode_string (shape.mode), shape.type, nr_pages); vm =____vm_create (shape); -vm_userspace_mem_region_add (vm,VM_MEM_SRC_ANONYMOUS ,0 ,0 , nr_pages,0 ); +if (shape.type ==KVM_X86_SNP_VM ) + flags |=KVM_MEM_GUEST_MEMFD ; + +vm_userspace_mem_region_add (vm,VM_MEM_SRC_ANONYMOUS ,0 ,0 , nr_pages, flags);for (i =0 ; i <NR_MEM_REGIONS ; i++) vm->memslots[i] =0 ;
Signature · 1 line
2.43.0
PATCH v6 8/9 KVM: selftests: Abstractions for SEV to decouple policy from type
In reply to Pratik R. SampatIn preparation for SNP, cleanup the smoke test to decouple deriving type from policy. Introduce, wrappers for SEV and SEV-ES types to abstract the parametrized launch tests calls and reduce verbosity.
No functional change intended.
---
v5..v6:
* Collected tags from Srikanth.
--- .../selftests/kvm/x86/sev_smoke_test.c | 50 ++++++++++++------- 1 file changed, 33 insertions(+), 17 deletions(-)
tools/testing/selftests/kvm/x86/sev_smoke_test.c +33 -17
@@ -61,7 +61,7 @@ static void compare_xsave(u8 *from_host, u8 *from_guest)abort (); } -static void test_sync_vmsa (uint32_t policy) +static void __test_sync_vmsa (uint32_t type,uint64_t policy) {struct kvm_vcpu *vcpu;struct kvm_vm *vm;
@@ -71,7 +71,7 @@ static void test_sync_vmsa(uint32_t policy)double x87val =M_PI ;struct kvm_xsave __attribute__((aligned (64 ))) xsave = {0 }; - vm =vm_sev_create_with_one_vcpu (KVM_X86_SEV_ES_VM , guest_code_xsave, &vcpu); + vm =vm_sev_create_with_one_vcpu (type, guest_code_xsave, &vcpu); gva =vm_vaddr_alloc_shared (vm,PAGE_SIZE ,KVM_UTIL_MIN_VADDR ,MEM_REGION_TEST_DATA ); hva =addr_gva2hva (vm, gva);
@@ -88,7 +88,7 @@ static void test_sync_vmsa(uint32_t policy) : "ymm4", "st", "st(1)", "st(2)", "st(3)", "st(4)", "st(5)", "st(6)", "st(7)");vcpu_xsave_set (vcpu, &xsave); -vm_sev_launch (vm,SEV_POLICY_ES | policy,NULL ); +vm_sev_launch (vm, policy,NULL );/* This page is shared, so make it decrypted. */ memset (hva,0 ,4096 );
@@ -107,14 +107,12 @@ static void test_sync_vmsa(uint32_t policy)kvm_vm_free (vm); } -static void test_sev (void *guest_code,uint64_t policy) +static void __test_sev (void *guest_code,uint32_t type,uint64_t policy) {struct kvm_vcpu *vcpu;struct kvm_vm *vm;struct ucall uc; -uint32_t type = policy &SEV_POLICY_ES ?KVM_X86_SEV_ES_VM :KVM_X86_SEV_VM ; - vm =vm_sev_create_with_one_vcpu (type, guest_code, &vcpu);/* TODO: Validate the measurement is as expected. */
@@ -149,6 +147,21 @@ static void test_sev(void *guest_code, uint64_t policy)kvm_vm_free (vm); } +static void test_sev (uint64_t policy) +{ +__test_sev (guest_sev_code,KVM_X86_SEV_VM , policy); +} + +static void test_sev_es (uint64_t policy) +{ +__test_sev (guest_sev_es_code,KVM_X86_SEV_ES_VM , policy); +} + +static void test_sync_vmsa_sev_es (uint64_t policy) +{ +__test_sync_vmsa (KVM_X86_SEV_ES_VM , policy); +} +static void guest_shutdown_code (void ) {struct desc_ptr idt;
@@ -160,16 +173,14 @@ static void guest_shutdown_code(void) __asm__ __volatile__("ud2" ); } -static void test_sev_es_shutdown (void ) +static void __test_sev_shutdown (uint32_t type,uint64_t policy) {struct kvm_vcpu *vcpu;struct kvm_vm *vm; -uint32_t type =KVM_X86_SEV_ES_VM ; - vm =vm_sev_create_with_one_vcpu (type, guest_shutdown_code, &vcpu); -vm_sev_launch (vm,SEV_POLICY_ES ,NULL ); +vm_sev_launch (vm, policy,NULL );vcpu_run (vcpu); TEST_ASSERT(vcpu->run->exit_reason == KVM_EXIT_SHUTDOWN,
@@ -179,25 +190,30 @@ static void test_sev_es_shutdown(void)kvm_vm_free (vm); } +static void test_sev_es_shutdown (uint64_t policy) +{ +__test_sev_shutdown (KVM_X86_SEV_ES_VM ,SEV_POLICY_ES ); +} +int main (int argc,char *argv[]) {const u64 xf_mask =XFEATURE_MASK_X87_AVX ;TEST_REQUIRE (kvm_cpu_has (X86_FEATURE_SEV )); -test_sev (guest_sev_code,SEV_POLICY_NO_DBG ); -test_sev (guest_sev_code,0 ); +test_sev (SEV_POLICY_NO_DBG ); +test_sev (0 );if (kvm_cpu_has (X86_FEATURE_SEV_ES )) { -test_sev (guest_sev_es_code,SEV_POLICY_ES |SEV_POLICY_NO_DBG ); -test_sev (guest_sev_es_code,SEV_POLICY_ES ); +test_sev_es (SEV_POLICY_ES |SEV_POLICY_NO_DBG ); +test_sev_es (SEV_POLICY_ES ); -test_sev_es_shutdown (); +test_sev_es_shutdown (SEV_POLICY_ES );if (kvm_has_cap (KVM_CAP_XCRS ) && (xgetbv (0 ) &kvm_cpu_supported_xcr0 () & xf_mask) == xf_mask) { -test_sync_vmsa (0 ); -test_sync_vmsa (SEV_POLICY_NO_DBG ); +test_sync_vmsa_sev_es (SEV_POLICY_ES ); +test_sync_vmsa_sev_es (SEV_POLICY_NO_DBG |SEV_POLICY_ES ); } }
Signature · 1 line
2.43.0
PATCH v6 9/9 KVM: selftests: Add a basic SEV-SNP smoke test
In reply to Pratik R. SampatExtend sev_smoke_test to also run a minimal SEV-SNP smoke test that initializes and sets up private memory regions required to run a simple SEV-SNP guest.
Similar to its SEV-ES smoke test counterpart, this also does not support GHCB and ucall yet and uses the GHCB MSR protocol to trigger an exit of the type KVM_EXIT_SYSTEM_EVENT.
---
v5..v6:
* Rename KVM CPU feature X86_FEATURE_SNP to X86_FEATURE_SEV_SNP (Nikunj)
* Collected tags from Srikanth.
--- .../selftests/kvm/x86/sev_smoke_test.c | 42 +++++++++++++++++++ 1 file changed, 42 insertions(+)
tools/testing/selftests/kvm/x86/sev_smoke_test.c +42 -0
@@ -16,6 +16,18 @@#define XFEATURE_MASK_X87_AVX (XFEATURE_MASK_FP | XFEATURE_MASK_SSE | XFEATURE_MASK_YMM) +static void guest_snp_code (void ) +{ +uint64_t sev_msr =rdmsr (MSR_AMD64_SEV ); + +GUEST_ASSERT (sev_msr &MSR_AMD64_SEV_ENABLED ); +GUEST_ASSERT (sev_msr &MSR_AMD64_SEV_ES_ENABLED ); +GUEST_ASSERT (sev_msr &MSR_AMD64_SEV_SNP_ENABLED ); + +wrmsr (MSR_AMD64_SEV_ES_GHCB ,GHCB_MSR_TERM_REQ ); +VMGEXIT (); +} +static void guest_sev_es_code (void ) {/* TODO: Check CPUID after GHCB-based hypercall support is added. */
@@ -157,11 +169,21 @@ static void test_sev_es(uint64_t policy)__test_sev (guest_sev_es_code,KVM_X86_SEV_ES_VM , policy); } +static void test_snp (uint64_t policy) +{ +__test_sev (guest_snp_code,KVM_X86_SNP_VM , policy); +} +static void test_sync_vmsa_sev_es (uint64_t policy) {__test_sync_vmsa (KVM_X86_SEV_ES_VM , policy); } +static void test_sync_vmsa_snp (uint64_t policy) +{ +__test_sync_vmsa (KVM_X86_SNP_VM , policy); +} +static void guest_shutdown_code (void ) {struct desc_ptr idt;
@@ -195,6 +217,11 @@ static void test_sev_es_shutdown(uint64_t policy)__test_sev_shutdown (KVM_X86_SEV_ES_VM ,SEV_POLICY_ES ); } +static void test_snp_shutdown (uint64_t policy) +{ +__test_sev_shutdown (KVM_X86_SNP_VM , policy); +} +int main (int argc,char *argv[]) {const u64 xf_mask =XFEATURE_MASK_X87_AVX ;
@@ -217,5 +244,20 @@ int main(int argc, char *argv[]) } } +if (kvm_cpu_has (X86_FEATURE_SEV_SNP )) { +uint64_t snp_policy =snp_default_policy (); + +test_snp (snp_policy); +/* Test minimum firmware level */ +test_snp (snp_policy |SNP_FW_VER_MAJOR (SNP_MIN_API_MAJOR ) | +SNP_FW_VER_MINOR (SNP_MIN_API_MINOR )); + +test_snp_shutdown (snp_policy); + +if (kvm_has_cap (KVM_CAP_XCRS ) && + (xgetbv (0 ) &kvm_cpu_supported_xcr0 () & xf_mask) == xf_mask) +test_sync_vmsa_snp (snp_policy); + } +return 0 ; }
Signature · 1 line
2.43.0
Sean Christopherson
maintainerRe: [PATCH v6 9/9] KVM: selftests: Add a basic SEV-SNP smoke test
tools/testing/selftests/kvm/x86/sev_smoke_test.c int main(int argc, char *argv[]) · line 253
Quoted 11 lines · Pratik R. Sampat
tools/testing/selftests/kvm/x86/sev_smoke_test.c +7
-0@@ -217,5 +244,20 @@ int main(int argc, char *argv[]) } } +if (kvm_cpu_has (X86_FEATURE_SEV_SNP )) { +uint64_t snp_policy =snp_default_policy (); + +test_snp (snp_policy); +/* Test minimum firmware level */ +test_snp (snp_policy |SNP_FW_VER_MAJOR (SNP_MIN_API_MAJOR ) | +SNP_FW_VER_MINOR (SNP_MIN_API_MINOR ));
Ah, this is where the firmware policy stuff is used. Refresh me, can userspace request _any_ major/minor as the min, and expect failure if the version isn't supported? If so, the test should iterate over the major/minor combinations that are guaranteed to fail. And if userspace can query the supported minor/major, the test should iterate over all the happy versions too.
Unless there's nothing interesting to test, I would move the major/minor stuff to a separate patch.
tools/testing/selftests/kvm/x86/sev_smoke_test.c int main(int argc, char *argv[]) · line 259
Quoted 6 lines
tools/testing/selftests/kvm/x86/sev_smoke_test.c +6
-0+ +test_snp_shutdown (snp_policy); + +if (kvm_has_cap (KVM_CAP_XCRS ) && + (xgetbv (0 ) &kvm_cpu_supported_xcr0 () & xf_mask) == xf_mask) +test_sync_vmsa_snp (snp_policy);
This is all copy+paste from SEV-ES tests, minus SEV_POLICY_NO_DBG. There's gotta be a way to dedup this code.
Something like this?
static void needs_a_better_name(uint32_t type, uint64_t policy)
{
const u64 xf_mask = XFEATURE_MASK_X87_AVX;
test_sev(guest_sev_code, policy | SEV_POLICY_NO_DBG);
test_sev(guest_sev_code, policy);
if (type == KVM_X86_SEV_VM)
return;
test_sev_shutdown(policy);
if (kvm_has_cap(KVM_CAP_XCRS) &&
(xgetbv(0) & kvm_cpu_supported_xcr0() & xf_mask) == xf_mask) {
test_sync_vmsa(policy);
test_sync_vmsa(policy | SEV_POLICY_NO_DBG);
}
}int main(int argc, char *argv[])
{
TEST_REQUIRE(kvm_cpu_has(X86_FEATURE_SEV));
needs_a_better_name(KVM_X86_SEV_VM, 0);
if (kvm_cpu_has(X86_FEATURE_SEV_ES))
needs_a_better_name(KVM_X86_SEV_ES_VM, 0);
if (kvm_cpu_has(X86_FEATURE_SEV_SNP))
needs_a_better_name(KVM_X86_SEV_SNP_VM, 0);
return 0;
}Re: [PATCH v6 9/9] KVM: selftests: Add a basic SEV-SNP smoke test
Quoted 5 lines · Sean Christopherson
Quoted 4 lines · Pratik R. Sampat
(quoted diff) +0
-0@@ -217,5 +244,20 @@ int main(int argc, char *argv[]) } }
Quoted 14 lines
tools/testing/selftests/kvm/x86/sev_smoke_test.c int main(int argc, char *argv[]) · line 253
Quoted 7 lines
tools/testing/selftests/kvm/x86/sev_smoke_test.c +7
-0+if (kvm_cpu_has (X86_FEATURE_SEV_SNP )) { +uint64_t snp_policy =snp_default_policy (); + +test_snp (snp_policy); +/* Test minimum firmware level */ +test_snp (snp_policy |SNP_FW_VER_MAJOR (SNP_MIN_API_MAJOR ) | +SNP_FW_VER_MINOR (SNP_MIN_API_MINOR ));Ah, this is where the firmware policy stuff is used. Refresh me, can userspace request _any_ major/minor as the min, and expect failure if the version isn't supported? If so, the test should iterate over the major/minor combinations that are guaranteed to fail. And if userspace can query the supported minor/major, the test should iterate over all the happy versions too.
Yes, any policy greater than the min policy (defined in sev-dev.c) should be supported. The sad path tests were intended to be added in the upcoming negative test patch series so that we could have the proper infrastructure to handle and report failures.
Quoted 2 lines
Unless there's nothing interesting to test, I would move the major/minor stuff to a separate patch.
Would you rather prefer I do the happy tests here (something like - min_policy and min_policy + 1?) and defer the failure tests for the next patchset? Or, I can remove policy testing from here entirely and introduce it only when the sad path testing infrastructure is ready, so that we can test this completely at once?
Quoted 33 lines
tools/testing/selftests/kvm/x86/sev_smoke_test.c int main(int argc, char *argv[]) · line 259
Quoted 7 lines
tools/testing/selftests/kvm/x86/sev_smoke_test.c +6
-0+ +test_snp_shutdown (snp_policy); + +if (kvm_has_cap (KVM_CAP_XCRS ) && + (xgetbv (0 ) &kvm_cpu_supported_xcr0 () & xf_mask) == xf_mask) +test_sync_vmsa_snp (snp_policy);This is all copy+paste from SEV-ES tests, minus
SEV_POLICY_NO_DBG. There's gotta be a way to dedup this code.Something like this?
static void
needs_a_better_name(uint32_t type, uint64_t policy){ const u64 xf_mask = XFEATURE_MASK_X87_AVX; test_sev(guest_sev_code, policy | SEV_POLICY_NO_DBG); test_sev(guest_sev_code, policy); if (type == KVM_X86_SEV_VM) return; test_sev_shutdown(policy); if (kvm_has_cap(KVM_CAP_XCRS) && (xgetbv(0) & kvm_cpu_supported_xcr0() & xf_mask) == xf_mask) { test_sync_vmsa(policy); test_sync_vmsa(policy | SEV_POLICY_NO_DBG); } }int
main(int argc, char *argv[])
Quoted 13 lines
{
TEST_REQUIRE(kvm_cpu_has(X86_FEATURE_SEV));
needs_a_better_name(KVM_X86_SEV_VM, 0);
if (kvm_cpu_has(X86_FEATURE_SEV_ES))
needs_a_better_name(KVM_X86_SEV_ES_VM, 0);
if (kvm_cpu_has(X86_FEATURE_SEV_SNP))
needs_a_better_name(KVM_X86_SEV_SNP_VM, 0);
return 0;
}Sure, I can definitely clean this up so that we have less duplication of code all around for this test.
Thanks again!
Pratik
Sean Christopherson
maintainerRe: [PATCH v6 9/9] KVM: selftests: Add a basic SEV-SNP smoke test
Quoted 28 lines · Pratik Rajesh Sampat
Quoted 5 lines · Sean Christopherson
Quoted 4 lines · Pratik R. Sampat
(quoted diff) +0
-0@@ -217,5 +244,20 @@ int main(int argc, char *argv[]) } }Quoted 14 lines
tools/testing/selftests/kvm/x86/sev_smoke_test.c int main(int argc, char *argv[]) · line 253
Quoted 7 lines
tools/testing/selftests/kvm/x86/sev_smoke_test.c +7
-0+if (kvm_cpu_has (X86_FEATURE_SEV_SNP )) { +uint64_t snp_policy =snp_default_policy (); + +test_snp (snp_policy); +/* Test minimum firmware level */ +test_snp (snp_policy |SNP_FW_VER_MAJOR (SNP_MIN_API_MAJOR ) | +SNP_FW_VER_MINOR (SNP_MIN_API_MINOR ));Ah, this is where the firmware policy stuff is used. Refresh me, can userspace request _any_ major/minor as the min, and expect failure if the version isn't supported? If so, the test should iterate over the major/minor combinations that are guaranteed to fail. And if userspace can query the supported minor/major, the test should iterate over all the happy versions too.
Yes, any policy greater than the min policy (defined in
sev-dev.c) should be supported. The sad path tests were intended to be added in the upcoming negative test patch series so that we could have the proper infrastructure to handle and report failures.
Quoted 8 lines
Quoted 2 lines
Unless there's nothing interesting to test, I would move the major/minor stuff to a separate patch.
Would you rather prefer I do the happy tests here (something like -
min_policyandmin_policy+ 1?) and defer the failure tests for the next patchset? Or, I can remove policy testing from here entirely and introduce it only when the sad path testing infrastructure is ready, so that we can test this completely at once?
Let's do the latter. For the initial series, do the bare minimum so that we can get that merged, and then focus on the min API version stuff in a separate series. The version testing shouldn't be terribly complex, but it doesn't seem like it's entirely trivial either, and I don't want it to block the base SNP support.
Re: [PATCH v6 9/9] KVM: selftests: Add a basic SEV-SNP smoke test
Quoted 38 lines · Sean Christopherson
Quoted 28 lines · Pratik Rajesh Sampat
Quoted 5 lines · Sean Christopherson
Quoted 4 lines · Pratik R. Sampat
(quoted diff) +0
-0@@ -217,5 +244,20 @@ int main(int argc, char *argv[]) } }Quoted 14 lines
tools/testing/selftests/kvm/x86/sev_smoke_test.c int main(int argc, char *argv[]) · line 253
Quoted 7 lines
tools/testing/selftests/kvm/x86/sev_smoke_test.c +7
-0+if (kvm_cpu_has (X86_FEATURE_SEV_SNP )) { +uint64_t snp_policy =snp_default_policy (); + +test_snp (snp_policy); +/* Test minimum firmware level */ +test_snp (snp_policy |SNP_FW_VER_MAJOR (SNP_MIN_API_MAJOR ) | +SNP_FW_VER_MINOR (SNP_MIN_API_MINOR ));Ah, this is where the firmware policy stuff is used. Refresh me, can userspace request _any_ major/minor as the min, and expect failure if the version isn't supported? If so, the test should iterate over the major/minor combinations that are guaranteed to fail. And if userspace can query the supported minor/major, the test should iterate over all the happy versions too.
Yes, any policy greater than the min policy (defined in
sev-dev.c) should be supported. The sad path tests were intended to be added in the upcoming negative test patch series so that we could have the proper infrastructure to handle and report failures.Quoted 8 lines
Quoted 2 lines
Unless there's nothing interesting to test, I would move the major/minor stuff to a separate patch.
Would you rather prefer I do the happy tests here (something like -
min_policyandmin_policy+ 1?) and defer the failure tests for the next patchset? Or, I can remove policy testing from here entirely and introduce it only when the sad path testing infrastructure is ready, so that we can test this completely at once?
Quoted 4 lines
Let's do the latter. For the initial series, do the bare minimum so that we can get that merged, and then focus on the min API version stuff in a separate series. The version testing shouldn't be terribly complex, but it doesn't seem like it's entirely trivial either, and I don't want it to block the base SNP support.
Sure thing, will do.
Thanks!