From: "Aithal, Srikanth" <sraithal@amd.com>
To: "Pratik R. Sampat" <prsampat@amd.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
kvm@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kselftest@vger.kernel.org
Cc: seanjc@google.com, pbonzini@redhat.com, thomas.lendacky@amd.com,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, shuah@kernel.org, pgonda@google.com,
ashish.kalra@amd.com, nikunj@amd.com, michael.roth@amd.com
Subject: Re: [PATCH v5 0/9] Basic SEV-SNP Selftests
Date: Wed, 29 Jan 2025 21:19:59 +0530 [thread overview]
Message-ID: <8e7d8172-879e-4a28-8438-343b1c386ec9@amd.com> (raw)
In-Reply-To: <20250123220100.339867-1-prsampat@amd.com>
On 1/24/2025 3:30 AM, Pratik R. Sampat wrote:
> 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
>
> v4..v5:
> * 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
>
Tested-by: Srikanth Aithal <sraithal@amd.com>
> v3..v4:
> https://lore.kernel.org/kvm/20241114234104.128532-1-pratikrajesh.sampat@amd.com/
> * 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/20240905124107.6954-1-pratikrajesh.sampat@amd.com/
> * 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(-)
>
prev parent reply other threads:[~2025-01-29 15:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 22:00 [PATCH v5 0/9] Basic SEV-SNP Selftests Pratik R. Sampat
2025-01-23 22:00 ` [PATCH v5 1/9] KVM: SEV: Disable SEV-SNP on FW validation failure Pratik R. Sampat
2025-01-24 10:03 ` Nikunj A Dadhania
2025-01-23 22:00 ` [PATCH v5 2/9] KVM: SEV: Disable SEV on platform init failure Pratik R. Sampat
2025-01-24 9:56 ` Nikunj A. Dadhania
2025-01-24 17:03 ` Pratik Rajesh Sampat
2025-01-23 22:00 ` [PATCH v5 3/9] KVM: selftests: SEV-SNP test for KVM_SEV_INIT2 Pratik R. Sampat
2025-01-28 12:13 ` Nikunj A Dadhania
2025-01-28 17:35 ` Pratik Rajesh Sampat
2025-01-23 22:00 ` [PATCH v5 4/9] KVM: selftests: Add VMGEXIT helper Pratik R. Sampat
2025-01-24 9:18 ` Gupta, Pankaj
2025-01-23 22:00 ` [PATCH v5 5/9] KVM: selftests: Introduce SEV VM type check Pratik R. Sampat
2025-01-23 22:00 ` [PATCH v5 6/9] KVM: selftests: Add library support for interacting with SNP Pratik R. Sampat
2025-01-23 22:00 ` [PATCH v5 7/9] KVM: selftests: Force GUEST_MEMFD flag for SNP VM type Pratik R. Sampat
2025-01-23 22:00 ` [PATCH v5 8/9] KVM: selftests: Abstractions for SEV to decouple policy from type Pratik R. Sampat
2025-01-23 22:01 ` [PATCH v5 9/9] KVM: selftests: Add a basic SEV-SNP smoke test Pratik R. Sampat
2025-01-29 15:49 ` Aithal, Srikanth [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=8e7d8172-879e-4a28-8438-343b1c386ec9@amd.com \
--to=sraithal@amd.com \
--cc=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=nikunj@amd.com \
--cc=pbonzini@redhat.com \
--cc=pgonda@google.com \
--cc=prsampat@amd.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
/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