public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Pratik R. Sampat" <prsampat@amd.com>
To: <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>, <sraithal@amd.com>,
	<prsampat@amd.com>
Subject: [PATCH v5 4/9] KVM: selftests: Add VMGEXIT helper
Date: Thu, 23 Jan 2025 16:00:55 -0600	[thread overview]
Message-ID: <20250123220100.339867-5-prsampat@amd.com> (raw)
In-Reply-To: <20250123220100.339867-1-prsampat@amd.com>

Abstract rep vmmcall coded into the VMGEXIT helper for the sev
library.

No functional change intended.

Signed-off-by: Pratik R. Sampat <prsampat@amd.com>
---
 tools/testing/selftests/kvm/include/x86/sev.h    | 2 ++
 tools/testing/selftests/kvm/x86/sev_smoke_test.c | 2 +-
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/tools/testing/selftests/kvm/include/x86/sev.h b/tools/testing/selftests/kvm/include/x86/sev.h
index 82c11c81a956..e7df5d0987f6 100644
--- a/tools/testing/selftests/kvm/include/x86/sev.h
+++ b/tools/testing/selftests/kvm/include/x86/sev.h
@@ -27,6 +27,8 @@ enum sev_guest_state {
 
 #define GHCB_MSR_TERM_REQ	0x100
 
+#define VMGEXIT()		{ __asm__ __volatile__("rep; vmmcall"); }
+
 void sev_vm_launch(struct kvm_vm *vm, uint32_t policy);
 void sev_vm_launch_measure(struct kvm_vm *vm, uint8_t *measurement);
 void sev_vm_launch_finish(struct kvm_vm *vm);
diff --git a/tools/testing/selftests/kvm/x86/sev_smoke_test.c b/tools/testing/selftests/kvm/x86/sev_smoke_test.c
index a1a688e75266..38f647fe55d2 100644
--- a/tools/testing/selftests/kvm/x86/sev_smoke_test.c
+++ b/tools/testing/selftests/kvm/x86/sev_smoke_test.c
@@ -27,7 +27,7 @@ static void guest_sev_es_code(void)
 	 * force "termination" to signal "done" via the GHCB MSR protocol.
 	 */
 	wrmsr(MSR_AMD64_SEV_ES_GHCB, GHCB_MSR_TERM_REQ);
-	__asm__ __volatile__("rep; vmmcall");
+	VMGEXIT();
 }
 
 static void guest_sev_code(void)
-- 
2.43.0


  parent reply	other threads:[~2025-01-23 22:01 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 ` Pratik R. Sampat [this message]
2025-01-24  9:18   ` [PATCH v5 4/9] KVM: selftests: Add VMGEXIT helper 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 ` [PATCH v5 0/9] Basic SEV-SNP Selftests Aithal, Srikanth

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=20250123220100.339867-5-prsampat@amd.com \
    --to=prsampat@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=seanjc@google.com \
    --cc=shuah@kernel.org \
    --cc=sraithal@amd.com \
    --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