From: Carlos Bilbao <carlos.bilbao@amd.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
Anup Patel <anup@brainfault.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.linux.dev, kvm-riscv@lists.infradead.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Vishal Annapurve <vannapurve@google.com>,
Ackerley Tng <ackerleytng@google.com>,
Andrew Jones <andrew.jones@linux.dev>,
Tom Lendacky <thomas.lendacky@amd.com>,
Michael Roth <michael.roth@amd.com>,
Peter Gonda <pgonda@google.com>,
Itaru Kitayama <itaru.kitayama@fujitsu.com>,
"Giani, Dhaval" <dhaval.giani@amd.com>
Subject: Re: [PATCH v9 00/11] KVM: selftests: Add SEV and SEV-ES smoke tests
Date: Mon, 26 Feb 2024 11:06:48 -0600 [thread overview]
Message-ID: <5e360765-3398-4b72-ba7c-4df0958bc5d3@amd.com> (raw)
In-Reply-To: <20240223004258.3104051-1-seanjc@google.com>
Hello,
On 2/22/24 18:42, Sean Christopherson wrote:
> Add basic SEV and SEV-ES smoke tests. Unlike the intra-host migration tests,
> this one actually runs a small chunk of code in the guest.
>
> Unless anyone strongly objects to the quick and dirty approach I've taken for
> SEV-ES, I'll get all of this queued for 6.9 soon-ish.
>
> As for _why_ I added the quick-and-dirty SEV-ES testcase, I have a series to
> cleanup __svm_sev_es_vcpu_run(), and found out that apparently I have a version
> of OVMF that doesn't quite have to the right <something> for SEV-ES, and so I
> could even get a "real" VM to reach KVM_RUN. I assumed (correctly, yay!) that
> hacking together a selftest would be faster than figuring out what firmware
> magic I am missing.
Tested-by: Carlos Bilbao <carlos.bilbao@amd.com>
>
> v9:
> - Drop is_kvm_sev_supported() and rely purely on KVM capabilities.
> - Check X86_FEATURE_SEV to ensure SEV is actually enabled.
> - Collect tags. [Carlos, Itaru]
>
> v8:
> - https://lore.kernel.org/all/cc9a1951-e76c-470d-a4d1-8ad67bae5794@amd.com
> - Undo the kvm.h uAPI breakage.
> - Take advantage of "struct vm_shape", introduced by the guest_memfd
> selftests, to simply tracking the SEV/SEV-ES subtypes.
> - Rename the test to "sev_smoke_test" instead of "sev_all_boot_test",
> as the "all" is rather nonsensical, and the test isn't booting anything
> in the traditional sense of the word.
> - Drop vm->protected and instead add an arch hook to query if the VM has
> protected memory.
> - Assert that the target memory region supports protected memory when
> allocating protected memory.
> - Allocate protected_phy_pages for memory regions if and only if the VM
> supports protected memory.
> - Rename kvm_host.h to kvm_util_arch.h, and move it to selftests/kvm where
> it belongs.
> - Fix up some SoB goofs.
> - Convert the intrahost SEV/SEV-ES migration tests to use common ioctl()
> wrappers.
>
> Ackerley Tng (1):
> KVM: selftests: Add a macro to iterate over a sparsebit range
>
> Michael Roth (2):
> KVM: selftests: Make sparsebit structs const where appropriate
> KVM: selftests: Add support for protected vm_vaddr_* allocations
>
> Peter Gonda (5):
> KVM: selftests: Add support for allocating/managing protected guest
> memory
> KVM: selftests: Explicitly ucall pool from shared memory
> KVM: selftests: Allow tagging protected memory in guest page tables
> KVM: selftests: Add library for creating and interacting with SEV
> guests
> KVM: selftests: Add a basic SEV smoke test
>
> Sean Christopherson (3):
> KVM: selftests: Extend VM creation's @shape to allow control of VM
> subtype
> KVM: selftests: Use the SEV library APIs in the intra-host migration
> test
> KVM: selftests: Add a basic SEV-ES smoke test
>
> tools/testing/selftests/kvm/Makefile | 2 +
> .../kvm/include/aarch64/kvm_util_arch.h | 7 ++
> .../selftests/kvm/include/kvm_util_base.h | 50 +++++++-
> .../kvm/include/riscv/kvm_util_arch.h | 7 ++
> .../kvm/include/s390x/kvm_util_arch.h | 7 ++
> .../testing/selftests/kvm/include/sparsebit.h | 56 ++++++---
> .../kvm/include/x86_64/kvm_util_arch.h | 23 ++++
> .../selftests/kvm/include/x86_64/processor.h | 8 ++
> .../selftests/kvm/include/x86_64/sev.h | 107 ++++++++++++++++
> tools/testing/selftests/kvm/lib/kvm_util.c | 67 ++++++++--
> tools/testing/selftests/kvm/lib/sparsebit.c | 48 ++++----
> .../testing/selftests/kvm/lib/ucall_common.c | 3 +-
> .../selftests/kvm/lib/x86_64/processor.c | 32 ++++-
> tools/testing/selftests/kvm/lib/x86_64/sev.c | 114 ++++++++++++++++++
> .../selftests/kvm/x86_64/sev_migrate_tests.c | 67 ++++------
> .../selftests/kvm/x86_64/sev_smoke_test.c | 88 ++++++++++++++
> 16 files changed, 583 insertions(+), 103 deletions(-)
> create mode 100644 tools/testing/selftests/kvm/include/aarch64/kvm_util_arch.h
> create mode 100644 tools/testing/selftests/kvm/include/riscv/kvm_util_arch.h
> create mode 100644 tools/testing/selftests/kvm/include/s390x/kvm_util_arch.h
> create mode 100644 tools/testing/selftests/kvm/include/x86_64/kvm_util_arch.h
> create mode 100644 tools/testing/selftests/kvm/include/x86_64/sev.h
> create mode 100644 tools/testing/selftests/kvm/lib/x86_64/sev.c
> create mode 100644 tools/testing/selftests/kvm/x86_64/sev_smoke_test.c
>
>
> base-commit: 60eedcfceda9db46f1b333e5e1aa9359793f04fb
Thanks,
Carlos
next prev parent reply other threads:[~2024-02-26 17:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 0:42 Sean Christopherson
2024-02-23 0:42 ` [PATCH v9 01/11] KVM: selftests: Extend VM creation's @shape to allow control of VM subtype Sean Christopherson
2024-02-23 0:42 ` [PATCH v9 02/11] KVM: selftests: Make sparsebit structs const where appropriate Sean Christopherson
2024-02-23 0:42 ` [PATCH v9 03/11] KVM: selftests: Add a macro to iterate over a sparsebit range Sean Christopherson
2024-02-23 0:42 ` [PATCH v9 04/11] KVM: selftests: Add support for allocating/managing protected guest memory Sean Christopherson
2024-02-23 0:42 ` [PATCH v9 05/11] KVM: selftests: Add support for protected vm_vaddr_* allocations Sean Christopherson
2024-02-23 0:42 ` [PATCH v9 06/11] KVM: selftests: Explicitly ucall pool from shared memory Sean Christopherson
2024-02-23 0:42 ` [PATCH v9 07/11] KVM: selftests: Allow tagging protected memory in guest page tables Sean Christopherson
2024-02-28 0:14 ` Xiaoyao Li
2024-02-28 2:12 ` Sean Christopherson
2024-02-29 0:53 ` Sean Christopherson
2024-02-23 0:42 ` [PATCH v9 08/11] KVM: selftests: Add library for creating and interacting with SEV guests Sean Christopherson
2024-02-23 0:42 ` [PATCH v9 09/11] KVM: selftests: Use the SEV library APIs in the intra-host migration test Sean Christopherson
2024-02-23 0:42 ` [PATCH v9 10/11] KVM: selftests: Add a basic SEV smoke test Sean Christopherson
2024-02-23 0:42 ` [PATCH v9 11/11] KVM: selftests: Add a basic SEV-ES " Sean Christopherson
2024-02-26 17:06 ` Carlos Bilbao [this message]
2024-02-27 2:21 ` [PATCH v9 00/11] KVM: selftests: Add SEV and SEV-ES smoke tests Sean Christopherson
2024-02-28 22:40 ` Sean Christopherson
2024-02-29 0:55 ` 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=5e360765-3398-4b72-ba7c-4df0958bc5d3@amd.com \
--to=carlos.bilbao@amd.com \
--cc=ackerleytng@google.com \
--cc=andrew.jones@linux.dev \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=borntraeger@linux.ibm.com \
--cc=dhaval.giani@amd.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=itaru.kitayama@fujitsu.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=michael.roth@amd.com \
--cc=oliver.upton@linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pbonzini@redhat.com \
--cc=pgonda@google.com \
--cc=seanjc@google.com \
--cc=thomas.lendacky@amd.com \
--cc=vannapurve@google.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
Powered by JetHome