All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: lkp@lists.01.org
Subject: Re: [KVM] feb627e8d6: kernel-selftests.kvm.vmx_pmu_msrs_test.fail
Date: Wed, 15 Dec 2021 16:58:56 +0100	[thread overview]
Message-ID: <87czlxvozj.fsf@redhat.com> (raw)
In-Reply-To: <20211215154643.GE34913@xsang-OptiPlex-9020>

[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]

kernel test robot <oliver.sang@intel.com> writes:

> Greeting,
>
> FYI, we noticed the following commit (built with gcc-9):
>
> commit: feb627e8d6f69c9a319fe279710959efb3eba873 ("KVM: x86: Forbid KVM_SET_CPUID{,2} after KVM_RUN")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>

...

>
> # selftests: kvm: vmx_pmu_msrs_test
> # ==== Test Assertion Failure ====
> #   lib/x86_64/processor.c:874: rc == 0
> #   pid=10415 tid=10415 errno=22 - Invalid argument
> #      1	0x000000000040b24f: vcpu_set_cpuid at processor.c:873
> #      2	0x000000000040260a: main at vmx_pmu_msrs_test.c:115
> #      3	0x00007f07e1aec09a: ?? ??:0
> #      4	0x0000000000402759: _start at ??:?
> #   KVM_SET_CPUID2 failed, rc: -1 errno: 22
> not ok 33 selftests: kvm: vmx_pmu_msrs_test # exit=254
>

Hm, I'm pretty sure I've tested feb627e8d6f6 on both Intel and AMD and I
don't remember seeing this failure :-( . vmx_pmu_msrs_test test does
KVM_SET_CPUID after KVM_RUN and thus needs to be fixed too. Will send a
patch shortly.

-- 
Vitaly

WARNING: multiple messages have this Message-ID (diff)
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	lkp@lists.01.org, lkp@intel.com, xudong.hao@intel.com,
	kernel test robot <oliver.sang@intel.com>
Subject: Re: [KVM]  feb627e8d6: kernel-selftests.kvm.vmx_pmu_msrs_test.fail
Date: Wed, 15 Dec 2021 16:58:56 +0100	[thread overview]
Message-ID: <87czlxvozj.fsf@redhat.com> (raw)
In-Reply-To: <20211215154643.GE34913@xsang-OptiPlex-9020>

kernel test robot <oliver.sang@intel.com> writes:

> Greeting,
>
> FYI, we noticed the following commit (built with gcc-9):
>
> commit: feb627e8d6f69c9a319fe279710959efb3eba873 ("KVM: x86: Forbid KVM_SET_CPUID{,2} after KVM_RUN")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>

...

>
> # selftests: kvm: vmx_pmu_msrs_test
> # ==== Test Assertion Failure ====
> #   lib/x86_64/processor.c:874: rc == 0
> #   pid=10415 tid=10415 errno=22 - Invalid argument
> #      1	0x000000000040b24f: vcpu_set_cpuid at processor.c:873
> #      2	0x000000000040260a: main at vmx_pmu_msrs_test.c:115
> #      3	0x00007f07e1aec09a: ?? ??:0
> #      4	0x0000000000402759: _start at ??:?
> #   KVM_SET_CPUID2 failed, rc: -1 errno: 22
> not ok 33 selftests: kvm: vmx_pmu_msrs_test # exit=254
>

Hm, I'm pretty sure I've tested feb627e8d6f6 on both Intel and AMD and I
don't remember seeing this failure :-( . vmx_pmu_msrs_test test does
KVM_SET_CPUID after KVM_RUN and thus needs to be fixed too. Will send a
patch shortly.

-- 
Vitaly


  reply	other threads:[~2021-12-15 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 15:46 [KVM] feb627e8d6: kernel-selftests.kvm.vmx_pmu_msrs_test.fail kernel test robot
2021-12-15 15:46 ` kernel test robot
2021-12-15 15:58 ` Vitaly Kuznetsov [this message]
2021-12-15 15:58   ` Vitaly Kuznetsov

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=87czlxvozj.fsf@redhat.com \
    --to=vkuznets@redhat.com \
    --cc=lkp@lists.01.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 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.