public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ricardo Koller <ricarkol@google.com>
To: Jim Mattson <jmattson@google.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: selftests: Fix nested SVM tests when built with clang
Date: Wed, 29 Sep 2021 18:30:03 -0700	[thread overview]
Message-ID: <YVUTG0n1i1n/RpL4@google.com> (raw)
In-Reply-To: <20210930003649.4026553-1-jmattson@google.com>

On Wed, Sep 29, 2021 at 05:36:49PM -0700, Jim Mattson wrote:
> Though gcc conveniently compiles a simple memset to "rep stos," clang
> prefers to call the libc version of memset. If a test is dynamically
> linked, the libc memset isn't available in L1 (nor is the PLT or the
> GOT, for that matter). Even if the test is statically linked, the libc
> memset may choose to use some CPU features, like AVX, which may not be
> enabled in L1. Note that __builtin_memset doesn't solve the problem,
> because (a) the compiler is free to call memset anyway, and (b)
> __builtin_memset may also choose to use features like AVX, which may
> not be available in L1.
> 
> To avoid a myriad of problems, use an explicit "rep stos" to clear the
> VMCB in generic_svm_setup(), which is called both from L0 and L1.
> 
> Reported-by: Ricardo Koller <ricarkol@google.com>
> Signed-off-by: Jim Mattson <jmattson@google.com>
> Fixes: 20ba262f8631a ("selftests: KVM: AMD Nested test infrastructure")
> ---
>  tools/testing/selftests/kvm/lib/x86_64/svm.c | 14 +++++++++++++-
>  1 file changed, 13 insertions(+), 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/kvm/lib/x86_64/svm.c b/tools/testing/selftests/kvm/lib/x86_64/svm.c
> index 2ac98d70d02b..161eba7cd128 100644
> --- a/tools/testing/selftests/kvm/lib/x86_64/svm.c
> +++ b/tools/testing/selftests/kvm/lib/x86_64/svm.c
> @@ -54,6 +54,18 @@ static void vmcb_set_seg(struct vmcb_seg *seg, u16 selector,
>  	seg->base = base;
>  }
>  
> +/*
> + * Avoid using memset to clear the vmcb, since libc may not be
> + * available in L1 (and, even if it is, features that libc memset may
> + * want to use, like AVX, may not be enabled).
> + */
> +static void clear_vmcb(struct vmcb *vmcb)
> +{
> +	int n = sizeof(*vmcb) / sizeof(u32);
> +
> +	asm volatile ("rep stosl" : "+c"(n), "+D"(vmcb) : "a"(0) : "memory");
> +}
> +
>  void generic_svm_setup(struct svm_test_data *svm, void *guest_rip, void *guest_rsp)
>  {
>  	struct vmcb *vmcb = svm->vmcb;
> @@ -70,7 +82,7 @@ void generic_svm_setup(struct svm_test_data *svm, void *guest_rip, void *guest_r
>  	wrmsr(MSR_EFER, efer | EFER_SVME);
>  	wrmsr(MSR_VM_HSAVE_PA, svm->save_area_gpa);
>  
> -	memset(vmcb, 0, sizeof(*vmcb));
> +	clear_vmcb(vmcb);
>  	asm volatile ("vmsave %0\n\t" : : "a" (vmcb_gpa) : "memory");
>  	vmcb_set_seg(&save->es, get_es(), 0, -1U, data_seg_attr);
>  	vmcb_set_seg(&save->cs, get_cs(), 0, -1U, code_seg_attr);
> -- 
> 2.33.0.685.g46640cef36-goog
> 

Reviewed-by: Ricardo Koller <ricarkol@google.com>

  reply	other threads:[~2021-09-30  1:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30  0:36 [PATCH] KVM: selftests: Fix nested SVM tests when built with clang Jim Mattson
2021-09-30  1:30 ` Ricardo Koller [this message]
2021-10-08 23:50   ` Jim Mattson
2021-10-21 20:24 ` Paolo Bonzini

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=YVUTG0n1i1n/RpL4@google.com \
    --to=ricarkol@google.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.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