From: "Pratik R. Sampat" <pratikrajesh.sampat@amd.com>
To: <kvm@vger.kernel.org>
Cc: <shuah@kernel.org>, <thomas.lendacky@amd.com>,
<michael.roth@amd.com>, <seanjc@google.com>,
<pbonzini@redhat.com>, <pgonda@google.com>,
<linux-kselftest@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [RFC 3/5] selftests: KVM: SEV IOCTL test
Date: Wed, 10 Jul 2024 17:05:38 -0500 [thread overview]
Message-ID: <20240710220540.188239-4-pratikrajesh.sampat@amd.com> (raw)
In-Reply-To: <20240710220540.188239-1-pratikrajesh.sampat@amd.com>
Introduce tests for sev and sev-es ioctl that exercises the boot path
of launch, update and finish on an invalid policy.
Signed-off-by: Pratik R. Sampat <pratikrajesh.sampat@amd.com>
---
.../selftests/kvm/x86_64/sev_smoke_test.c | 57 +++++++++++++++++++
1 file changed, 57 insertions(+)
diff --git a/tools/testing/selftests/kvm/x86_64/sev_smoke_test.c b/tools/testing/selftests/kvm/x86_64/sev_smoke_test.c
index 1a50a280173c..500c67b3793b 100644
--- a/tools/testing/selftests/kvm/x86_64/sev_smoke_test.c
+++ b/tools/testing/selftests/kvm/x86_64/sev_smoke_test.c
@@ -131,12 +131,69 @@ static void test_sync_vmsa(uint32_t type, uint32_t policy)
kvm_vm_free(vm);
}
+static void sev_guest_status_assert(struct kvm_vm *vm, uint32_t type)
+{
+ struct kvm_sev_guest_status status;
+ bool cond;
+ int ret;
+
+ ret = __vm_sev_ioctl(vm, KVM_SEV_GUEST_STATUS, &status);
+ cond = type == KVM_X86_SEV_VM ? !ret : ret;
+ TEST_ASSERT(cond,
+ "KVM_SEV_GUEST_STATUS should fail, invalid VM Type.");
+}
+
+static void test_sev_launch(void *guest_code, uint32_t type, uint64_t policy)
+{
+ struct kvm_vcpu *vcpu;
+ struct kvm_vm *vm;
+ struct ucall uc;
+ bool cond;
+ int ret;
+
+ vm = vm_sev_create_with_one_vcpu(type, guest_code, &vcpu);
+ ret = sev_vm_launch_start(vm, 0);
+ cond = type == KVM_X86_SEV_VM ? !ret : ret;
+ TEST_ASSERT(cond,
+ "KVM_SEV_LAUNCH_START should fail, invalid policy.");
+
+ ret = sev_vm_launch_update(vm, policy);
+ cond = type == KVM_X86_SEV_VM ? !ret : ret;
+ TEST_ASSERT(cond,
+ "KVM_SEV_LAUNCH_UPDATE should fail, invalid policy.");
+ sev_guest_status_assert(vm, type);
+
+ ret = sev_vm_launch_measure(vm, alloca(256));
+ cond = type == KVM_X86_SEV_VM ? !ret : ret;
+ TEST_ASSERT(cond,
+ "KVM_SEV_LAUNCH_MEASURE should fail, invalid policy.");
+ sev_guest_status_assert(vm, type);
+
+ ret = sev_vm_launch_finish(vm);
+ cond = type == KVM_X86_SEV_VM ? !ret : ret;
+ TEST_ASSERT(cond,
+ "KVM_SEV_LAUNCH_FINISH should fail, invalid policy.");
+ sev_guest_status_assert(vm, type);
+
+ vcpu_run(vcpu);
+ get_ucall(vcpu, &uc);
+ cond = type == KVM_X86_SEV_VM ?
+ vcpu->run->exit_reason == KVM_EXIT_IO :
+ vcpu->run->exit_reason == KVM_EXIT_FAIL_ENTRY;
+ TEST_ASSERT(cond,
+ "vcpu_run should fail, invalid policy.");
+
+ kvm_vm_free(vm);
+}
+
static void test_sev(void *guest_code, uint32_t type, uint64_t policy)
{
struct kvm_vcpu *vcpu;
struct kvm_vm *vm;
struct ucall uc;
+ test_sev_launch(guest_code, type, policy);
+
vm = vm_sev_create_with_one_vcpu(type, guest_code, &vcpu);
/* TODO: Validate the measurement is as expected. */
--
2.34.1
next prev parent reply other threads:[~2024-07-10 22:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 22:05 [RFC 0/5] SEV Kernel Selftests Pratik R. Sampat
2024-07-10 22:05 ` [RFC 1/5] selftests: KVM: Add a basic SNP smoke test Pratik R. Sampat
2024-07-11 15:16 ` Peter Gonda
2024-07-11 16:21 ` Sampat, Pratik Rajesh
2024-07-11 15:56 ` Tom Lendacky
2024-07-11 16:23 ` Sampat, Pratik Rajesh
2024-07-10 22:05 ` [RFC 2/5] selftests: KVM: Decouple SEV ioctls from asserts Pratik R. Sampat
2024-07-11 15:19 ` Peter Gonda
2024-07-11 16:11 ` Peter Gonda
2024-07-11 16:27 ` Sampat, Pratik Rajesh
2024-08-09 15:40 ` Sean Christopherson
2024-08-13 15:23 ` Pratik R. Sampat
2024-08-13 15:27 ` Sean Christopherson
2024-08-13 15:30 ` Pratik R. Sampat
2024-07-10 22:05 ` Pratik R. Sampat [this message]
2024-07-11 15:23 ` [RFC 3/5] selftests: KVM: SEV IOCTL test Peter Gonda
2024-07-11 16:23 ` Sampat, Pratik Rajesh
2024-07-11 18:34 ` Tom Lendacky
2024-07-11 20:02 ` Sampat, Pratik Rajesh
2024-08-09 15:45 ` Sean Christopherson
2024-08-13 15:23 ` Pratik R. Sampat
2024-07-10 22:05 ` [RFC 4/5] selftests: KVM: SNP " Pratik R. Sampat
2024-07-11 15:57 ` Peter Gonda
2024-07-11 16:27 ` Sampat, Pratik Rajesh
2024-08-09 15:48 ` Sean Christopherson
2024-08-13 15:23 ` Pratik R. Sampat
2024-07-10 22:05 ` [RFC 5/5] selftests: KVM: SEV-SNP test for KVM_SEV_INIT2 Pratik R. Sampat
2024-07-11 15:57 ` Peter Gonda
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=20240710220540.188239-4-pratikrajesh.sampat@amd.com \
--to=pratikrajesh.sampat@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--cc=pgonda@google.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=thomas.lendacky@amd.com \
/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
all inboxes | Powered by JetHome®