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,
Thomas Gleixner <tglx@linutronix.de>,
Li Huafei <lihuafei1@huawei.com>,
linux-perf-users@vger.kernel.org
Subject: Re: [linus:master] [perf/x86/intel] 25dfc9e357: kvm-unit-tests-qemu.pmu.fail
Date: Mon, 23 Sep 2024 10:49:58 +0800 [thread overview]
Message-ID: <61d6d709-209a-432a-94ee-e999c50c847e@linux.intel.com> (raw)
In-Reply-To: <f272389f-8565-4bdc-8727-8b37eaa82821@linux.intel.com>
On 9/20/2024 9:27 PM, Liang, Kan wrote:
>
> On 2024-09-20 3:50 a.m., kernel test robot wrote:
>>
>> Hello,
>>
>> kernel test robot noticed "kvm-unit-tests-qemu.pmu.fail" on:
>>
>> commit: 25dfc9e357af8aed1ca79b318a73f2c59c1f0b2b ("perf/x86/intel: Limit the period on Haswell")
> This should only impact the period wrote to a counter.
> There is no functional change.
>
> As far as I know, the kvm-unit-tests-qemu.pmu directly manipulates the
> counters. It should not be impacted by the perf changes. That's weird.
We found KUT/pmu test cases could cause many false positives, especially on
some new Platforms, like SPR/EMR. We already have a patch series to fix
these false positives, but unfortunately it's still not merged.
Here is the patch series link. Thanks.
https://lore.kernel.org/all/20240914101728.33148-1-dapeng1.mi@linux.intel.com/
>
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>>
>> [test failed on linus/master 3352633ce6b221d64bf40644d412d9670e7d56e3]
>> [test failed on linux-next/master 5acd9952f95fb4b7da6d09a3be39195a80845eb6]
>>
>> in testcase: kvm-unit-tests-qemu
>> version:
>> with following parameters:
>>
>>
>>
>>
>> compiler: gcc-12
>> test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (Haswell) with 16G 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/202409201525.4877023e-oliver.sang@intel.com
>>
>>
>> ...
>> ^[[32mPASS^[[0m msr (1836 tests)
>> ^[[31mFAIL^[[0m pmu (143 tests, 24 unexpected failures, 14 skipped) <---
> Is there a list to show which checks are failed?
>
> Thanks,
> Kan
>
>> ^[[32mPASS^[[0m pmu_lbr (3 tests)
>> ^[[33mSKIP^[[0m pmu_pebs (1 tests, 1 skipped)
>> ...
>>
>>
>>
>> The kernel config and materials to reproduce are available at:
>> https://download.01.org/0day-ci/archive/20240920/202409201525.4877023e-oliver.sang@intel.com
>>
>>
>>
next prev parent reply other threads:[~2024-09-23 2:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 7:50 [linus:master] [perf/x86/intel] 25dfc9e357: kvm-unit-tests-qemu.pmu.fail kernel test robot
2024-09-20 13:27 ` Liang, Kan
2024-09-23 2:49 ` Mi, Dapeng [this message]
2024-09-23 4:31 ` Oliver Sang
2024-09-24 2:17 ` Mi, Dapeng
2024-09-24 2:46 ` Oliver Sang
2024-09-24 3:16 ` 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=61d6d709-209a-432a-94ee-e999c50c847e@linux.intel.com \
--to=dapeng1.mi@linux.intel.com \
--cc=kan.liang@linux.intel.com \
--cc=lihuafei1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=tglx@linutronix.de \
/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.