From: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
To: "Liang, Kan" <kan.liang@linux.intel.com>,
kernel test robot <oliver.sang@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
Subject: Re: [linus:master] [perf/x86] 88ec7eedbb: kvm-unit-tests.pmu_lbr.fail
Date: Tue, 8 Apr 2025 10:13:07 +0800 [thread overview]
Message-ID: <418fff05-a0d9-4ead-b344-7b0b7fdb7f7f@linux.intel.com> (raw)
In-Reply-To: <f872c998-c076-4e09-8f7d-1ad29a065d4a@linux.intel.com>
On 4/7/2025 10:38 PM, Liang, Kan wrote:
>
> On 2025-04-07 1:07 a.m., kernel test robot wrote:
>>
>> 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:
> The one line patch only impacts the perf record.
> But the test case is for LBR on KVM. The case directly access the
> IA32_DEBUGCTLMSR to enable/disable LBRs. There is nothing related.
> It is probably a false alarm.
>
> + Dapeng
>
> Could you please take a look at the qemu test case?
Sure. I would investigate it later.
>
> Thanks,
> Kan>
>> 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
>>
>>
>>
prev parent reply other threads:[~2025-04-08 2:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 5:07 kernel test robot
2025-04-07 14:38 ` Liang, Kan
2025-04-08 2:13 ` Mi, Dapeng [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=418fff05-a0d9-4ead-b344-7b0b7fdb7f7f@linux.intel.com \
--to=dapeng1.mi@linux.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=oliver.sang@intel.com \
--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
all inboxes | Powered by JetHome®