From: kernel test robot <yi1.lai@intel.com>
To: Kevin Cheng <chengkev@google.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com, kvm@vger.kernel.org,
seanjc@google.com, pbonzini@redhat.com,
linux-kernel@vger.kernel.org, yosry@kernel.org,
Kevin Cheng <chengkev@google.com>,
yi1.lai@intel.com
Subject: Re: [PATCH] KVM: nVMX: Synthesize advanced VM-Exit info for emulated EPT Violations
Date: Sun, 15 Nov 2026 20:13:57 +0800 [thread overview]
Message-ID: <202611151806.4ddbcfeb-lkp@intel.com> (raw)
In-Reply-To: <20261029024005.575065-1-chengkev@google.com>
Hello,
kernel test robot noticed "kselftests.kvm.nested_tdp_fault_test.fail" on:
commit: 1a01388ba3bd52d1535b10bb5974059f9418cd9e ("[PATCH] KVM: nVMX: Synthesize advanced VM-Exit info for emulated EPT Violations")
url: https://github.com/intel-lab-lkp/linux/commits/Kevin-Cheng/KVM-nVMX-Synthesize-advanced-VM-Exit-info-for-emulated-EPT-Violations/20261029-024005
base: https://git.kernel.org/cgit/virt/kvm/kvm.git queue patch link: https://lore.kernel.org/all/20261029024005.575065-1-chengkev@google.com/
patch subject: [PATCH] KVM: nVMX: Synthesize advanced VM-Exit info for emulated EPT Violations
in testcase: kselftests
version: kselftests-x86_64-05441d697f7f-1_20261105
with following parameters:
group: kvm
config: x86_64-rhel-9.4-kselftests
compiler: gcc-14
test machine: 224 threads 2 sockets Intel(R) Xeon(R) Platinum 8480CTDX (Sapphire Rapids) with 256G 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 <yi1.lai@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202611151806.4ddbcfeb-lkp@intel.com
# selftests: kvm: nested_tdp_fault_test
# Random seed: 0x3ccb3ded
#
# ==== Test Assertion Failure ====
# x86/nested_tdp_fault_test.c:84: (exit_qual) == (((((1UL))) << (0)) | ((((1UL))) << (7)) | ((((1UL))) << (8)))
# pid=10529 tid=10529 errno=4 - Interrupted system call
# 1 0x0000000000413921: assert_on_unhandled_exception at processor.c:786
# 2 0x00000000004075e6: _vcpu_run at kvm_util.c:1770
# 3 (inlined by) vcpu_run at kvm_util.c:1781
# 4 0x0000000000403902: run_test at nested_tdp_fault_test.c:275
# 5 0x0000000000402c09: main at nested_tdp_fault_test.c:302
# 6 0x00007f102953aca7: ?? ??:0
# 7 0x00007f102953ad64: ?? ??:0
# 8 0x0000000000402d50: _start at ??:?
# Wanted EXIT_QUAL '0x181', got '0x581'
not ok 40 selftests: kvm: nested_tdp_fault_test # exit=254
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20261115/202611151806.4ddbcfeb-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-11-15 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 2:40 [PATCH] KVM: nVMX: Synthesize advanced VM-Exit info for emulated EPT Violations Kevin Cheng
2026-10-29 15:17 ` Jim Mattson
2026-11-15 12:13 ` 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=202611151806.4ddbcfeb-lkp@intel.com \
--to=yi1.lai@intel.com \
--cc=chengkev@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=yosry@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox