From: kernel test robot <oliver.sang@intel.com>
To: Tao Su <tao1.su@linux.intel.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Yi Lai <yi1.lai@intel.com>, <kvm@vger.kernel.org>,
<xudong.hao@intel.com>, <seanjc@google.com>,
<pbonzini@redhat.com>, <chao.gao@intel.com>,
<guang.zeng@intel.com>, <tao1.su@linux.intel.com>,
<oliver.sang@intel.com>
Subject: Re: [PATCH 2/2] KVM: x86: Clear X2APIC_ICR_UNUSED_12 after APIC-write VM-exit
Date: Sun, 24 Sep 2023 21:58:38 +0800 [thread overview]
Message-ID: <202309242109.43637c74-oliver.sang@intel.com> (raw)
In-Reply-To: <20230904013555.725413-3-tao1.su@linux.intel.com>
Hello,
kernel test robot noticed "kernel-selftests.kvm.xapic_state_test.fail" on:
commit: 6ccade077c151e719397b0a86f48554db9aa1c24 ("[PATCH 2/2] KVM: x86: Clear X2APIC_ICR_UNUSED_12 after APIC-write VM-exit")
url: https://github.com/intel-lab-lkp/linux/commits/Tao-Su/x86-apic-Introduce-X2APIC_ICR_UNUSED_12-for-x2APIC-mode/20230904-093801
patch link: https://lore.kernel.org/all/20230904013555.725413-3-tao1.su@linux.intel.com/
patch subject: [PATCH 2/2] KVM: x86: Clear X2APIC_ICR_UNUSED_12 after APIC-write VM-exit
in testcase: kernel-selftests
version: kernel-selftests-x86_64-60acb023-1_20230329
with following parameters:
group: kvm
compiler: gcc-12
test machine: 224 threads 2 sockets Intel(R) Xeon(R) Platinum 8480+ (Sapphire Rapids) with 256G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
besides, we also noticed kvm.smm_test.fail which keeps pass on parent.
83c02e23e21fec27 6ccade077c151e719397b0a86f4
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:6 100% 6:6 kernel-selftests.kvm.smm_test.fail
:6 100% 6:6 kernel-selftests.kvm.xapic_state_test.fail
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202309242109.43637c74-oliver.sang@intel.com
# timeout set to 120
# selftests: kvm: smm_test
# ==== Test Assertion Failure ====
# x86_64/smm_test.c:179: stage_reported == stage || stage_reported == SMRAM_STAGE
# pid=6354 tid=6354 errno=4 - Interrupted system call
# 1 0x00000000004026fc: main at smm_test.c:179
# 2 0x00007f08310cb189: ?? ??:0
# 3 0x00007f08310cb244: ?? ??:0
# 4 0x0000000000402810: _start at ??:?
# Unexpected stage: #3, got 4
not ok 25 selftests: kvm: smm_test # exit=254
...
# timeout set to 120
# selftests: kvm: xapic_state_test
# ==== Test Assertion Failure ====
# x86_64/xapic_state_test.c:78: __a == __b
# pid=7081 tid=7081 errno=4 - Interrupted system call
# 1 0x0000000000402a1f: ____test_icr at xapic_state_test.c:78
# 2 0x0000000000402c51: __test_icr at xapic_state_test.c:95 (discriminator 3)
# 3 (inlined by) test_icr at xapic_state_test.c:106 (discriminator 3)
# 4 0x0000000000402433: main at xapic_state_test.c:197
# 5 0x00007f8a0c660189: ?? ??:0
# 6 0x00007f8a0c660244: ?? ??:0
# 7 0x0000000000402640: _start at ??:?
# ASSERT_EQ(icr & ~APIC_ICR_BUSY, val & ~APIC_ICR_BUSY) failed.
# icr & ~APIC_ICR_BUSY is 0
# val & ~APIC_ICR_BUSY is 0x44000
not ok 47 selftests: kvm: xapic_state_test # exit=254
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20230924/202309242109.43637c74-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-09-24 13:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 1:35 [PATCH 0/2] KVM: x86: Fix a WARN in kvm_apic_send_ipi() Tao Su
2023-09-04 1:35 ` [PATCH 1/2] x86/apic: Introduce X2APIC_ICR_UNUSED_12 for x2APIC mode Tao Su
2023-09-04 2:58 ` Chao Gao
2023-09-04 3:03 ` Tao Su
2023-09-04 1:35 ` [PATCH 2/2] KVM: x86: Clear X2APIC_ICR_UNUSED_12 after APIC-write VM-exit Tao Su
2023-09-04 2:46 ` Chao Gao
2023-09-04 3:00 ` Tao Su
2023-09-04 4:16 ` kernel test robot
2023-09-04 5:02 ` Tao Su
2023-09-05 23:03 ` Sean Christopherson
2023-09-06 5:07 ` Tao Su
2023-09-06 22:17 ` Sean Christopherson
2023-09-07 9:56 ` Tao Su
2023-09-24 13:58 ` kernel test robot [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=202309242109.43637c74-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=chao.gao@intel.com \
--cc=guang.zeng@intel.com \
--cc=kvm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tao1.su@linux.intel.com \
--cc=xudong.hao@intel.com \
--cc=yi1.lai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox