From: kernel test robot <oliver.sang@intel.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Waiman Long <longman@redhat.com>, <linux-mm@kvack.org>,
<oliver.sang@intel.com>
Subject: [linus:master] [kmemleak] 39042079a0: kernel-selftests.kvm.memslot_perf_test.fail
Date: Thu, 25 Jan 2024 15:34:37 +0800 [thread overview]
Message-ID: <202401251429.d3dea02b-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "kernel-selftests.kvm.memslot_perf_test.fail" on:
commit: 39042079a0c241d09fa6fc3bb67c2ddf60011d0f ("kmemleak: avoid RCU stalls when freeing metadata for per-CPU pointers")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 9d64bf433c53cab2f48a3fff7a1f2a696bc5229a]
[test failed on linux-next/master ad5c60d66016e544c51ed98635a74073f761f45d]
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)
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/202401251429.d3dea02b-oliver.sang@intel.com
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240125/202401251429.d3dea02b-oliver.sang@intel.com
# timeout set to 120
# selftests: kvm: memslot_perf_test
# Testing map performance with 1 runs, 5 seconds each
# Memslot count too high for this test, decrease the cap (max is 8209)
#
# Testing unmap performance with 1 runs, 5 seconds each
# Test took 9.178259867s for slot setup + 5.035747214s all iterations
# Done 85 iterations, avg 0.059244084s each
# Best runtime result was 0.059244084s per iteration (with 85 iterations)
#
# Testing unmap chunked performance with 1 runs, 5 seconds each
# Test took 9.460993790s for slot setup + 5.001833746s all iterations
# Done 84 iterations, avg 0.059545639s each
# Best runtime result was 0.059545639s per iteration (with 84 iterations)
#
# Testing move active area performance with 1 runs, 5 seconds each
# Test took 9.235748282s for slot setup + 5.001305107s all iterations
# Done 4807 iterations, avg 0.001040421s each
# Best runtime result was 0.001040421s per iteration (with 4807 iterations)
#
# Testing move inactive area performance with 1 runs, 5 seconds each
# Test took 9.113425177s for slot setup + 5.001150112s all iterations
# Done 4534 iterations, avg 0.001103032s each
# Best runtime result was 0.001103032s per iteration (with 4534 iterations)
#
# Testing RW performance with 1 runs, 5 seconds each
#
not ok 71 selftests: kvm: memslot_perf_test # TIMEOUT 120 seconds
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-01-25 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 7:34 kernel test robot [this message]
2024-01-25 12:01 ` [linus:master] [kmemleak] 39042079a0: kernel-selftests.kvm.memslot_perf_test.fail Catalin Marinas
2024-01-26 6:35 ` Oliver Sang
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=202401251429.d3dea02b-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=longman@redhat.com \
--cc=oe-lkp@lists.linux.dev \
/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.