linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pratik Rajesh Sampat <prsampat@amd.com>
To: Sean Christopherson <seanjc@google.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	kvm@vger.kernel.org, linux-crypto@vger.kernel.org,
	linux-kselftest@vger.kernel.org, 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,
	pankaj.gupta@amd.com, michael.roth@amd.com, sraithal@amd.com
Subject: Re: [PATCH v6 4/9] KVM: selftests: Add VMGEXIT helper
Date: Fri, 14 Feb 2025 12:09:30 -0600	[thread overview]
Message-ID: <d8217a1a-4aba-4e26-9b87-2fd9b6bf92f2@amd.com> (raw)
In-Reply-To: <Z6wAclXklofHtY__@google.com>

On 2/11/25 7:59 PM, Sean Christopherson wrote:
> On Mon, Feb 03, 2025, Pratik R. Sampat wrote:
>> Abstract rep vmmcall coded into the VMGEXIT helper for the sev
>> library.
>>
>> No functional change intended.
>>
>> Reviewed-by: Pankaj Gupta <pankaj.gupta@amd.com>
>> Tested-by: Srikanth Aithal <sraithal@amd.com>
>> Signed-off-by: Pratik R. Sampat <prsampat@amd.com>
>> ---
>> v5..v6:
>>
>> * Collected tags from Pankaj and Srikanth.
>> ---
>>  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"); }
> 
> Please make this a proper inline function, there's no reason to use a macro.

Sure, I can make this an inline function.

  reply	other threads:[~2025-02-14 18:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03 22:31 [PATCH v6 0/9] Basic SEV-SNP Selftests Pratik R. Sampat
2025-02-03 22:31 ` [PATCH v6 1/9] KVM: SEV: Disable SEV-SNP on FW validation failure Pratik R. Sampat
2025-02-12  1:54   ` Sean Christopherson
2025-02-14 18:07     ` Pratik Rajesh Sampat
2025-02-03 22:31 ` [PATCH v6 2/9] KVM: SEV: Disable SEV on platform init failure Pratik R. Sampat
2025-02-12  1:58   ` Sean Christopherson
2025-02-14 18:09     ` Pratik Rajesh Sampat
2025-02-03 22:31 ` [PATCH v6 3/9] KVM: selftests: SEV-SNP test for KVM_SEV_INIT2 Pratik R. Sampat
2025-02-03 22:32 ` [PATCH v6 4/9] KVM: selftests: Add VMGEXIT helper Pratik R. Sampat
2025-02-12  1:59   ` Sean Christopherson
2025-02-14 18:09     ` Pratik Rajesh Sampat [this message]
2025-02-03 22:32 ` [PATCH v6 5/9] KVM: selftests: Introduce SEV VM type check Pratik R. Sampat
2025-02-03 22:32 ` [PATCH v6 6/9] KVM: selftests: Add library support for interacting with SNP Pratik R. Sampat
2025-02-12  2:12   ` Sean Christopherson
2025-02-14 18:12     ` Pratik Rajesh Sampat
2025-02-19 16:55       ` Sean Christopherson
2025-02-20 16:56         ` Pratik Rajesh Sampat
2025-02-03 22:32 ` [PATCH v6 7/9] KVM: selftests: Force GUEST_MEMFD flag for SNP VM type Pratik R. Sampat
2025-02-03 22:32 ` [PATCH v6 8/9] KVM: selftests: Abstractions for SEV to decouple policy from type Pratik R. Sampat
2025-02-03 22:32 ` [PATCH v6 9/9] KVM: selftests: Add a basic SEV-SNP smoke test Pratik R. Sampat
2025-02-12  2:31   ` Sean Christopherson
2025-02-14 18:14     ` Pratik Rajesh Sampat
2025-02-19  0:54       ` Sean Christopherson
2025-02-19 14:58         ` Pratik Rajesh Sampat

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=d8217a1a-4aba-4e26-9b87-2fd9b6bf92f2@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=pankaj.gupta@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;
as well as URLs for NNTP newsgroup(s).