linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Kan Liang <kan.liang@linux.intel.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>,
	Ravi Bangoria <ravi.bangoria@amd.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	<linux-perf-users@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linus:master] [perf/x86]  88ec7eedbb: kvm-unit-tests.pmu_lbr.fail
Date: Mon, 7 Apr 2025 13:07:17 +0800	[thread overview]
Message-ID: <202504071232.3c2fa7d5-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]



Hello,

kernel test robot noticed "kvm-unit-tests.pmu_lbr.fail" on:

commit: 88ec7eedbbd21cad38707620ad6c48a4e9a87c18 ("perf/x86: Fix low freqency setting issue")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master

[test failed on linus/master      0a87d6bb6fd274cde3bf217a821153714374198f]
[test failed on linux-next/master fefb886b1344e222b3218f3c0165b0fd770e8b88]

in testcase: kvm-unit-tests
version: kvm-unit-tests-x86_64-69574079-1_20250322
with following parameters:


config: x86_64-rhel-9.4-func
compiler: gcc-12
test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (Haswell) with 8G 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/202504071232.3c2fa7d5-lkp@intel.com


...
^[[32mPASS^[[0m pmu (143 tests, 14 skipped)
^[[31mFAIL^[[0m pmu_lbr (2 tests, 1 unexpected failures)   <---
^[[33mSKIP^[[0m pmu_pebs (1 tests, 1 skipped)
...


one log is attached.


The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250407/202504071232.3c2fa7d5-lkp@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


[-- Attachment #2: pmu_lbr.log --]
[-- Type: text/plain, Size: 560 bytes --]

timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/pmu_lbr.flat -smp 1 -cpu host,migratable=no # -initrd /tmp/tmp.1JDHego9zM
enabling apic
smp: waiting for 0 APs
paging enabled
cr0 = 80010011
cr3 = 1007000
cr4 = 20
PMU version:		 2
LBR version:		 4
PASS: The number of guest LBR entries is good.
FAIL: The guest LBR FROM_IP/TO_IP values are good.
SUMMARY: 2 tests, 1 unexpected failures


             reply	other threads:[~2025-04-07  5:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07  5:07 kernel test robot [this message]
2025-04-07 14:38 ` [linus:master] [perf/x86] 88ec7eedbb: kvm-unit-tests.pmu_lbr.fail Liang, Kan
2025-04-08  2:13   ` Mi, Dapeng

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=202504071232.3c2fa7d5-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mingo@kernel.org \
    --cc=oe-lkp@lists.linux.dev \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@amd.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;
as well as URLs for NNTP newsgroup(s).