public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Aithal, Srikanth" <sraithal@amd.com>
To: "Pratik R. Sampat" <pratikrajesh.sampat@amd.com>, kvm@vger.kernel.org
Cc: seanjc@google.com, pbonzini@redhat.com, pgonda@google.com,
	thomas.lendacky@amd.com, michael.roth@amd.com, shuah@kernel.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/9] SEV Kernel Selftests
Date: Tue, 27 Aug 2024 11:14:04 +0530	[thread overview]
Message-ID: <c72cb617-2c0d-4d38-abef-cda1dcf03c06@amd.com> (raw)
In-Reply-To: <20240816192310.117456-1-pratikrajesh.sampat@amd.com>

On 8/17/2024 12:53 AM, Pratik R. Sampat wrote:
> This series primarily introduces SEV-SNP test for the kernel selftest
> framework. It tests boot, ioctl, pre fault, and fallocate in various
> combinations to exercise both positive and negative launch flow paths.
> 
> Patch 1 - Adds a wrapper for the ioctl calls that decouple ioctl and
> asserts which enables the use of negative test cases. No functional
> change intended.
> Patch 2 - Extend the sev smoke tests to use the SNP specific ioctl
> calls and sets up memory to boot a SNP guest VM
> Patch 3 - Adds SNP to shutdown testing
> Patch 4, 5 - Tests the ioctl path for SEV, SEV-ES and SNP
> Patch 6 - Adds support for SNP in KVM_SEV_INIT2 tests
> Patch 7,8,9 - Enable Prefault tests for SEV, SEV-ES and SNP
> 
> The patchset is rebased on top of kvm/queue and and over the
> "KVM: selftests: Add SEV-ES shutdown test" patch.
> https://lore.kernel.org/kvm/20240709182936.146487-1-pgonda@google.com/
> 
> v2:
> 1. Add SMT parsing check to populate SNP policy flags
> 2. Extend Peter Gonda's shutdown test to include SNP
> 3. Introduce new tests for prefault which include exercising prefault,
>     fallocate, hole-punch in various combinations.
> 4. Decouple ioctl patch reworked to introduce private variants of the
>     the functions that call into the ioctl. Also reordered the patch for
>     it to arrive first so that new APIs are not written right after
>     their introduction.
> 5. General cleanups - adding comments, avoiding local booleans, better
>     error message. Suggestions incorporated from Peter, Tom, and Sean.
> 

Tested-by: Srikanth Aithal <sraithal@amd.com>


      parent reply	other threads:[~2024-08-27  5:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-16 19:23 [PATCH v2 0/9] SEV Kernel Selftests Pratik R. Sampat
2024-08-16 19:23 ` [PATCH v2 1/9] KVM: selftests: Decouple SEV ioctls from asserts Pratik R. Sampat
2024-08-16 19:23 ` [PATCH v2 2/9] KVM: selftests: Add a basic SNP smoke test Pratik R. Sampat
2024-08-16 19:23 ` [PATCH v2 3/9] KVM: selftests: Add SNP to shutdown testing Pratik R. Sampat
2024-08-16 19:23 ` [PATCH v2 4/9] KVM: selftests: SEV IOCTL test Pratik R. Sampat
2024-08-16 19:23 ` [PATCH v2 5/9] KVM: selftests: SNP " Pratik R. Sampat
2024-08-16 19:23 ` [PATCH v2 6/9] KVM: selftests: SEV-SNP test for KVM_SEV_INIT2 Pratik R. Sampat
2024-08-16 19:23 ` [PATCH v2 7/9] KVM: selftests: Add interface to manually flag protected/encrypted ranges Pratik R. Sampat
2024-08-16 19:23 ` [PATCH v2 8/9] KVM: selftests: Add a CoCo-specific test for KVM_PRE_FAULT_MEMORY Pratik R. Sampat
2024-08-20  6:24   ` Aithal, Srikanth
2024-08-22 16:32     ` Pratik R. Sampat
2024-08-23 20:23   ` Pratik R. Sampat
2024-08-23 22:16     ` Tom Lendacky
2024-08-26 22:00       ` Pratik R. Sampat
2024-08-16 19:23 ` [PATCH v2 9/9] KVM: selftests: Interleave fallocate " Pratik R. Sampat
2024-08-19 19:43 ` [PATCH v2 0/9] SEV Kernel Selftests Peter Gonda
2024-08-27  5:44 ` 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=c72cb617-2c0d-4d38-abef-cda1dcf03c06@amd.com \
    --to=sraithal@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=pratikrajesh.sampat@amd.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