From: kernel test robot <oliver.sang@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Yiwei Zhang <zzyiwei@google.com>, Yan Zhao <yan.y.zhao@intel.com>,
Kevin Tian <kevin.tian@intel.com>,
Xiangfei Ma <xiangfeix.ma@intel.com>,
Yongwei Ma <yongwei.ma@intel.com>, <kvm@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [linux-next:master] [KVM] 377b2f359d: kvm-unit-tests-qemu.vmx.fail
Date: Fri, 14 Jun 2024 15:13:58 +0800 [thread overview]
Message-ID: <202406141424.5053d640-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "kvm-unit-tests-qemu.vmx.fail" on:
commit: 377b2f359d1f71c75f8cc352b5c81f2210312d83 ("KVM: VMX: Always honor guest PAT on CPUs that support self-snoop")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 6906a84c482f098d31486df8dc98cead21cce2d0]
in testcase: kvm-unit-tests-qemu
version:
with following parameters:
compiler: gcc-13
test machine: 128 threads 2 sockets Intel(R) Xeon(R) Platinum 8358 CPU @ 2.60GHz (Ice Lake) with 128G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
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/202406141424.5053d640-oliver.sang@intel.com
^[[31mFAIL^[[0m vmx (65128 tests, 2 unexpected failures, 2 expected failures, 5 skipped)
as a comparison, on parent, we observed
^[[32mPASS^[[0m vmx (430039 tests, 2 expected failures, 5 skipped)
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240614/202406141424.5053d640-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-06-14 7:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 7:13 kernel test robot [this message]
2024-06-14 15:15 ` 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=202406141424.5053d640-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=seanjc@google.com \
--cc=xiangfeix.ma@intel.com \
--cc=yan.y.zhao@intel.com \
--cc=yongwei.ma@intel.com \
--cc=zzyiwei@google.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