All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: David Matlack <dmatlack@google.com>, kvm@vger.kernel.org
Cc: Andrew Jones <drjones@redhat.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>
Subject: Re: [PATCH] KVM: selftests: Ignore CPUID.0DH.1H in get_cpuid_test
Date: Mon, 24 May 2021 14:31:03 +0200	[thread overview]
Message-ID: <08787663-92ef-2e6d-5c65-2baff1b25f27@redhat.com> (raw)
In-Reply-To: <20210519211345.3944063-1-dmatlack@google.com>

On 19/05/21 23:13, David Matlack wrote:
> Similar to CPUID.0DH.0H this entry depends on the vCPU's XCR0 register
> and IA32_XSS MSR. Since this test does not control for either before
> assigning the vCPU's CPUID, these entries will not necessarily match
> the supported CPUID exposed by KVM.
> 
> This fixes get_cpuid_test on Cascade Lake CPUs.
> 
> Signed-off-by: David Matlack <dmatlack@google.com>
> ---
>   tools/testing/selftests/kvm/x86_64/get_cpuid_test.c | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/tools/testing/selftests/kvm/x86_64/get_cpuid_test.c b/tools/testing/selftests/kvm/x86_64/get_cpuid_test.c
> index 9b78e8889638..8c77537af5a1 100644
> --- a/tools/testing/selftests/kvm/x86_64/get_cpuid_test.c
> +++ b/tools/testing/selftests/kvm/x86_64/get_cpuid_test.c
> @@ -19,7 +19,12 @@ struct {
>   	u32 function;
>   	u32 index;
>   } mangled_cpuids[] = {
> +	/*
> +	 * These entries depend on the vCPU's XCR0 register and IA32_XSS MSR,
> +	 * which are not controlled for by this test.
> +	 */
>   	{.function = 0xd, .index = 0},
> +	{.function = 0xd, .index = 1},
>   };
>   
>   static void test_guest_cpuids(struct kvm_cpuid2 *guest_cpuid)
> 

Queued, thanks.

Paolo


      parent reply	other threads:[~2021-05-24 12:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 21:13 [PATCH] KVM: selftests: Ignore CPUID.0DH.1H in get_cpuid_test David Matlack
2021-05-19 21:14 ` David Matlack
2021-05-24 12:31 ` Paolo Bonzini [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=08787663-92ef-2e6d-5c65-2baff1b25f27@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=dmatlack@google.com \
    --cc=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=vkuznets@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.