From: Sean Christopherson <seanjc@google.com>
To: Peter Gonda <pgonda@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
marcorr@google.com, michael.roth@amd.com,
thomas.lendacky@amd.com, joro@8bytes.org, mizhang@google.com,
pbonzini@redhat.com, andrew.jones@linux.dev
Subject: Re: [V4 8/8] KVM: selftests: Add simple sev vm testing
Date: Thu, 6 Oct 2022 18:31:18 +0000 [thread overview]
Message-ID: <Yz8e9t0L//pXD9S9@google.com> (raw)
In-Reply-To: <20220829171021.701198-9-pgonda@google.com>
On Mon, Aug 29, 2022, Peter Gonda wrote:
> + for (i = 0; i <= NR_SYNCS; ++i) {
> + vcpu_run(vcpu);
> + switch (get_ucall(vcpu, &uc)) {
> + case UCALL_SYNC:
> + continue;
> + case UCALL_DONE:
> + return;
> + case UCALL_ABORT:
> + TEST_ASSERT(false, "%s at %s:%ld\n\tvalues: %#lx, %#lx",
> + (const char *)uc.args[0], __FILE__,
> + uc.args[1], uc.args[2], uc.args[3]);
REPORT_GUEST_ASSERT
> + default:
> + TEST_ASSERT(
> + false, "Unexpected exit: %s",
> + exit_reason_str(vcpu->run->exit_reason));
TEST_FAIL
> + }
> + }
> +}
> +
> +static void guest_sev_code(void)
> +{
> + uint32_t eax, ebx, ecx, edx;
> + uint64_t sev_status;
> +
> + GUEST_SYNC(1);
> +
> + GUEST_ASSERT(this_cpu_has(X86_FEATURE_SEV));
> +
> + sev_status = rdmsr(MSR_AMD64_SEV);
> + GUEST_ASSERT((sev_status & 0x1) == 1);
Add a #define for the magic 0x1. And the "== 1" is unnecessary. Hmm, and the
querying of SEV/SEV-ES/etc status in MSR_AMD64_SEV should be done in helpers.
> +
> + GUEST_DONE();
> +}
> +
> +static struct sev_vm *setup_test_common(void *guest_code, uint64_t policy,
> + struct kvm_vcpu **vcpu)
> +{
> + uint8_t measurement[512];
> + struct sev_vm *sev;
> + struct kvm_vm *vm;
> + int i;
> +
> + sev = sev_vm_create(policy, TOTAL_PAGES);
> + TEST_ASSERT(sev, "sev_vm_create() failed to create VM\n");
See earlier comments on using TEST_REQUIRE.
> +
> + vm = sev->vm;
> +
> + /* Set up VCPU and initial guest kernel. */
> + *vcpu = vm_vcpu_add(vm, 0, guest_code);
> + kvm_vm_elf_load(vm, program_invocation_name);
> +
> + /* Allocations/setup done. Encrypt initial guest payload. */
> + sev_vm_launch(sev);
> +
> + /* Dump the initial measurement. A test to actually verify it would be nice. */
> + sev_vm_launch_measure(sev, measurement);
> + pr_info("guest measurement: ");
> + for (i = 0; i < 32; ++i)
> + pr_info("%02x", measurement[i]);
> + pr_info("\n");
> +
> + sev_vm_launch_finish(sev);
I believe this entire function gets replaced with
vm = ____vm_create_with_one_vcpu(VM_MODE_PXXV48_4K_SEV, &vcpu, 0,
guest_code);
> +
> + return sev;
> +}
> +
> +static void test_sev(void *guest_code, uint64_t policy)
> +{
> + struct sev_vm *sev;
> + struct kvm_vcpu *vcpu;
> +
> + sev = setup_test_common(guest_code, policy, &vcpu);
> +
> + /* Guest is ready to run. Do the tests. */
Comment doesn't add much value.
> + guest_run_loop(vcpu);
> +
> + pr_info("guest ran successfully\n");
Meh, the test passing is a good indication the test ran successfully.
> +
> + sev_vm_free(sev);
> +}
> +
> +int main(int argc, char *argv[])
> +{
> + /* SEV tests */
Again, stating the obvious.
> + test_sev(guest_sev_code, SEV_POLICY_NO_DBG);
> + test_sev(guest_sev_code, 0);
> +
> + return 0;
> +}
> --
> 2.37.2.672.g94769d06f0-goog
>
prev parent reply other threads:[~2022-10-06 18:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 17:10 [V4 0/8] KVM: selftests: Add simple SEV test Peter Gonda
2022-08-29 17:10 ` [V4 1/8] KVM: selftests: move vm_phy_pages_alloc() earlier in file Peter Gonda
2022-10-06 17:35 ` Sean Christopherson
2022-08-29 17:10 ` [V4 2/8] KVM: selftests: sparsebit: add const where appropriate Peter Gonda
2022-08-29 17:10 ` [V4 3/8] KVM: selftests: add hooks for managing encrypted guest memory Peter Gonda
2022-10-06 17:48 ` Sean Christopherson
2022-10-11 17:38 ` Peter Gonda
2022-08-29 17:10 ` [V4 4/8] KVM: selftests: handle encryption bits in page tables Peter Gonda
2022-10-06 17:34 ` Sean Christopherson
2022-08-29 17:10 ` [V4 5/8] KVM: selftests: add support for encrypted vm_vaddr_* allocations Peter Gonda
2022-08-29 17:10 ` [V4 6/8] KVM: selftests: add library for creating/interacting with SEV guests Peter Gonda
2022-10-06 18:25 ` Sean Christopherson
2022-10-17 16:32 ` Peter Gonda
2022-10-17 18:04 ` Sean Christopherson
2022-10-17 18:25 ` Peter Gonda
2022-10-17 20:34 ` Sean Christopherson
2022-10-18 14:59 ` Peter Gonda
2022-10-19 16:34 ` Sean Christopherson
2022-10-27 16:24 ` Peter Gonda
2022-10-27 17:59 ` Sean Christopherson
2022-10-27 18:34 ` Peter Gonda
2022-08-29 17:10 ` [V4 7/8] KVM: selftests: Update ucall pool to allocate from shared memory Peter Gonda
2022-08-29 17:10 ` [V4 8/8] KVM: selftests: Add simple sev vm testing Peter Gonda
2022-10-06 18:31 ` Sean Christopherson [this message]
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=Yz8e9t0L//pXD9S9@google.com \
--to=seanjc@google.com \
--cc=andrew.jones@linux.dev \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcorr@google.com \
--cc=michael.roth@amd.com \
--cc=mizhang@google.com \
--cc=pbonzini@redhat.com \
--cc=pgonda@google.com \
--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