From: Sean Christopherson <sean.j.christopherson@intel.com>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
lkp@lists.01.org, xudong.hao@intel.com
Subject: Re: [KVM] 6b6a864bd7: kernel-selftests.kvm.vmx_tsc_adjust_test.fail
Date: Mon, 11 May 2020 14:35:37 -0700 [thread overview]
Message-ID: <20200511213537.GG24052@linux.intel.com> (raw)
In-Reply-To: <20200511010926.GV5770@shao2-debian>
On Mon, May 11, 2020 at 09:09:26AM +0800, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 6b6a864bd7d7eb12a82ec6da1c2dd97a43f79449 ("[PATCH v2] KVM: nVMX: Tweak handling of failure code for nested VM-Enter failure")
> url: https://github.com/0day-ci/linux/commits/Sean-Christopherson/KVM-nVMX-Tweak-handling-of-failure-code-for-nested-VM-Enter-failure/20200429-052911
> base: https://git.kernel.org/cgit/virt/kvm/kvm.git linux-next
>
> in testcase: kernel-selftests
> with following parameters:
>
> group: kselftests-kvm
> ucode: 0x500002c
>
> test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
> test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
>
>
> on test machine: 192 threads Intel(R) Xeon(R) Platinum 9242 CPU @ 2.30GHz with 192G memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <rong.a.chen@intel.com>
>
>
>
> # selftests: kvm: vmx_tsc_adjust_test
> # ==== Test Assertion Failure ====
> # x86_64/vmx_tsc_adjust_test.c:153: false
> # pid=12157 tid=12157 - Interrupted system call
> # 1 0x000000000040116a: main at vmx_tsc_adjust_test.c:153
> # 2 0x00007fafd54bce0a: ?? ??:0
> # 3 0x00000000004011e9: _start at ??:?
> # Failed guest assert: (vmreadz(VM_EXIT_REASON) == (0x80000000 | 33))
> # IA32_TSC_ADJUST is -4294972240 (-1 * TSC_ADJUST_VALUE + -4944).
> not ok 14 selftests: kvm: vmx_tsc_adjust_test # exit=254
Ugh, missed the prepare_vmcs02() path. v3 incoming.
WARNING: multiple messages have this Message-ID (diff)
From: Sean Christopherson <sean.j.christopherson@intel.com>
To: lkp@lists.01.org
Subject: Re: [KVM] 6b6a864bd7: kernel-selftests.kvm.vmx_tsc_adjust_test.fail
Date: Mon, 11 May 2020 14:35:37 -0700 [thread overview]
Message-ID: <20200511213537.GG24052@linux.intel.com> (raw)
In-Reply-To: <20200511010926.GV5770@shao2-debian>
[-- Attachment #1: Type: text/plain, Size: 1806 bytes --]
On Mon, May 11, 2020 at 09:09:26AM +0800, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 6b6a864bd7d7eb12a82ec6da1c2dd97a43f79449 ("[PATCH v2] KVM: nVMX: Tweak handling of failure code for nested VM-Enter failure")
> url: https://github.com/0day-ci/linux/commits/Sean-Christopherson/KVM-nVMX-Tweak-handling-of-failure-code-for-nested-VM-Enter-failure/20200429-052911
> base: https://git.kernel.org/cgit/virt/kvm/kvm.git linux-next
>
> in testcase: kernel-selftests
> with following parameters:
>
> group: kselftests-kvm
> ucode: 0x500002c
>
> test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
> test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
>
>
> on test machine: 192 threads Intel(R) Xeon(R) Platinum 9242 CPU @ 2.30GHz with 192G memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <rong.a.chen@intel.com>
>
>
>
> # selftests: kvm: vmx_tsc_adjust_test
> # ==== Test Assertion Failure ====
> # x86_64/vmx_tsc_adjust_test.c:153: false
> # pid=12157 tid=12157 - Interrupted system call
> # 1 0x000000000040116a: main at vmx_tsc_adjust_test.c:153
> # 2 0x00007fafd54bce0a: ?? ??:0
> # 3 0x00000000004011e9: _start at ??:?
> # Failed guest assert: (vmreadz(VM_EXIT_REASON) == (0x80000000 | 33))
> # IA32_TSC_ADJUST is -4294972240 (-1 * TSC_ADJUST_VALUE + -4944).
> not ok 14 selftests: kvm: vmx_tsc_adjust_test # exit=254
Ugh, missed the prepare_vmcs02() path. v3 incoming.
next prev parent reply other threads:[~2020-05-11 21:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 17:32 [PATCH v2] KVM: nVMX: Tweak handling of failure code for nested VM-Enter failure Sean Christopherson
2020-04-28 18:47 ` Jim Mattson
2020-04-29 13:10 ` Vitaly Kuznetsov
2020-05-04 16:44 ` Paolo Bonzini
2020-05-11 1:09 ` [KVM] 6b6a864bd7: kernel-selftests.kvm.vmx_tsc_adjust_test.fail kernel test robot
2020-05-11 1:09 ` kernel test robot
2020-05-11 21:35 ` Sean Christopherson [this message]
2020-05-11 21:35 ` Sean Christopherson
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=20200511213537.GG24052@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=pbonzini@redhat.com \
--cc=rong.a.chen@intel.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=xudong.hao@intel.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.