linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [linus:master] [perf/x86/intel]  25dfc9e357: kvm-unit-tests-qemu.pmu.fail
@ 2024-09-20  7:50 kernel test robot
  2024-09-20 13:27 ` Liang, Kan
  0 siblings, 1 reply; 7+ messages in thread
From: kernel test robot @ 2024-09-20  7:50 UTC (permalink / raw)
  To: Kan Liang
  Cc: oe-lkp, lkp, linux-kernel, Thomas Gleixner, Li Huafei,
	linux-perf-users, oliver.sang



Hello,

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

commit: 25dfc9e357af8aed1ca79b318a73f2c59c1f0b2b ("perf/x86/intel: Limit the period on Haswell")
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)  <---
^[[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



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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [linus:master] [perf/x86/intel] 25dfc9e357: kvm-unit-tests-qemu.pmu.fail
  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
  2024-09-23  4:31   ` Oliver Sang
  0 siblings, 2 replies; 7+ messages in thread
From: Liang, Kan @ 2024-09-20 13:27 UTC (permalink / raw)
  To: kernel test robot
  Cc: oe-lkp, lkp, linux-kernel, Thomas Gleixner, Li Huafei,
	linux-perf-users, Dapeng Mi



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.

> 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
> 
> 
> 

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [linus:master] [perf/x86/intel] 25dfc9e357: kvm-unit-tests-qemu.pmu.fail
  2024-09-20 13:27 ` Liang, Kan
@ 2024-09-23  2:49   ` Mi, Dapeng
  2024-09-23  4:31   ` Oliver Sang
  1 sibling, 0 replies; 7+ messages in thread
From: Mi, Dapeng @ 2024-09-23  2:49 UTC (permalink / raw)
  To: Liang, Kan, kernel test robot
  Cc: oe-lkp, lkp, linux-kernel, Thomas Gleixner, Li Huafei,
	linux-perf-users


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
>>
>>
>>

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [linus:master] [perf/x86/intel] 25dfc9e357: kvm-unit-tests-qemu.pmu.fail
  2024-09-20 13:27 ` Liang, Kan
  2024-09-23  2:49   ` Mi, Dapeng
@ 2024-09-23  4:31   ` Oliver Sang
  2024-09-24  2:17     ` Mi, Dapeng
  1 sibling, 1 reply; 7+ messages in thread
From: Oliver Sang @ 2024-09-23  4:31 UTC (permalink / raw)
  To: Liang, Kan
  Cc: oe-lkp, lkp, linux-kernel, Thomas Gleixner, Li Huafei,
	linux-perf-users, Dapeng Mi, oliver.sang

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

hi, Kan,

On Fri, Sep 20, 2024 at 09:27:06AM -0400, Liang, Kan wrote:

> > ...
> > ^[[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?

I attached a pmu.log.

below failed which can pass on parent (v6.11-rc5)

FAIL: Intel: overflow: cntr-0
FAIL: Intel: overflow: status-0
FAIL: Intel: overflow: cntr-1
FAIL: Intel: overflow: status-1
FAIL: Intel: overflow: irq-1
FAIL: Intel: overflow: cntr-2
FAIL: Intel: overflow: status-2
FAIL: Intel: overflow: cntr-3
FAIL: Intel: overflow: status-3
FAIL: Intel: overflow: irq-3
FAIL: Intel: overflow: cntr-4
FAIL: Intel: overflow: status-4
FAIL: Intel: full-width writes: overflow: cntr-0
FAIL: Intel: full-width writes: overflow: status-0
FAIL: Intel: full-width writes: overflow: cntr-1
FAIL: Intel: full-width writes: overflow: status-1
FAIL: Intel: full-width writes: overflow: irq-1
FAIL: Intel: full-width writes: overflow: cntr-2
FAIL: Intel: full-width writes: overflow: status-2
FAIL: Intel: full-width writes: overflow: cntr-3
FAIL: Intel: full-width writes: overflow: status-3
FAIL: Intel: full-width writes: overflow: irq-3
FAIL: Intel: full-width writes: overflow: cntr-4
FAIL: Intel: full-width writes: overflow: status-4


> 
> 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
> > 
> > 
> > 

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

timeout -k 1s --foreground 90s /lkp/benchmarks/qemu/build/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.flat -smp 1 -cpu max # -initrd /tmp/tmp.WgbBni4GGX
enabling apic
smp: waiting for 0 APs
paging enabled
cr0 = 80010011
cr3 = 1007000
cr4 = 20
PASS: Expected #GP on RDPMC(64)
PMU version:         2
GP counters:         4
GP counter width:    48
Mask length:         7
Fixed counters:      3
Fixed counter width: 48
PASS: Intel: core cycles-0
PASS: Intel: core cycles-1
PASS: Intel: core cycles-2
PASS: Intel: core cycles-3
PASS: Intel: instructions-0
PASS: Intel: instructions-1
PASS: Intel: instructions-2
PASS: Intel: instructions-3
PASS: Intel: ref cycles-0
PASS: Intel: ref cycles-1
PASS: Intel: ref cycles-2
PASS: Intel: ref cycles-3
PASS: Intel: llc references-0
PASS: Intel: llc references-1
PASS: Intel: llc references-2
PASS: Intel: llc references-3
PASS: Intel: llc misses-0
PASS: Intel: llc misses-1
PASS: Intel: llc misses-2
PASS: Intel: llc misses-3
PASS: Intel: branches-0
PASS: Intel: branches-1
PASS: Intel: branches-2
PASS: Intel: branches-3
PASS: Intel: branch misses-0
PASS: Intel: branch misses-1
PASS: Intel: branch misses-2
PASS: Intel: branch misses-3
PASS: Intel: fixed-0
PASS: Intel: fixed-1
PASS: Intel: fixed-2
PASS: Intel: rdpmc: cntr-0
SKIP: Intel: rdpmc: fast-0
PASS: Intel: rdpmc: cntr-1
SKIP: Intel: rdpmc: fast-1
PASS: Intel: rdpmc: cntr-2
SKIP: Intel: rdpmc: fast-2
PASS: Intel: rdpmc: cntr-3
SKIP: Intel: rdpmc: fast-3
PASS: Intel: rdpmc: fixed cntr-0
SKIP: Intel: rdpmc: fixed fast-0
PASS: Intel: rdpmc: fixed cntr-1
SKIP: Intel: rdpmc: fixed fast-1
PASS: Intel: rdpmc: fixed cntr-2
SKIP: Intel: rdpmc: fixed fast-2
PASS: Intel: all counters
FAIL: Intel: overflow: cntr-0
FAIL: Intel: overflow: status-0
PASS: Intel: overflow: status clear-0
PASS: Intel: overflow: irq-0
FAIL: Intel: overflow: cntr-1
FAIL: Intel: overflow: status-1
PASS: Intel: overflow: status clear-1
FAIL: Intel: overflow: irq-1
FAIL: Intel: overflow: cntr-2
FAIL: Intel: overflow: status-2
PASS: Intel: overflow: status clear-2
PASS: Intel: overflow: irq-2
FAIL: Intel: overflow: cntr-3
FAIL: Intel: overflow: status-3
PASS: Intel: overflow: status clear-3
FAIL: Intel: overflow: irq-3
FAIL: Intel: overflow: cntr-4
FAIL: Intel: overflow: status-4
PASS: Intel: overflow: status clear-4
PASS: Intel: overflow: irq-4
PASS: Intel: cmask
PASS: Intel: running counter wrmsr: cntr
PASS: Intel: running counter wrmsr: status msr bit
PASS: Intel: full-width writes: core cycles-0
PASS: Intel: full-width writes: core cycles-1
PASS: Intel: full-width writes: core cycles-2
PASS: Intel: full-width writes: core cycles-3
PASS: Intel: full-width writes: instructions-0
PASS: Intel: full-width writes: instructions-1
PASS: Intel: full-width writes: instructions-2
PASS: Intel: full-width writes: instructions-3
PASS: Intel: full-width writes: ref cycles-0
PASS: Intel: full-width writes: ref cycles-1
PASS: Intel: full-width writes: ref cycles-2
PASS: Intel: full-width writes: ref cycles-3
PASS: Intel: full-width writes: llc references-0
PASS: Intel: full-width writes: llc references-1
PASS: Intel: full-width writes: llc references-2
PASS: Intel: full-width writes: llc references-3
PASS: Intel: full-width writes: llc misses-0
PASS: Intel: full-width writes: llc misses-1
PASS: Intel: full-width writes: llc misses-2
PASS: Intel: full-width writes: llc misses-3
PASS: Intel: full-width writes: branches-0
PASS: Intel: full-width writes: branches-1
PASS: Intel: full-width writes: branches-2
PASS: Intel: full-width writes: branches-3
PASS: Intel: full-width writes: branch misses-0
PASS: Intel: full-width writes: branch misses-1
PASS: Intel: full-width writes: branch misses-2
PASS: Intel: full-width writes: branch misses-3
PASS: Intel: full-width writes: fixed-0
PASS: Intel: full-width writes: fixed-1
PASS: Intel: full-width writes: fixed-2
PASS: Intel: full-width writes: rdpmc: cntr-0
SKIP: Intel: full-width writes: rdpmc: fast-0
PASS: Intel: full-width writes: rdpmc: cntr-1
SKIP: Intel: full-width writes: rdpmc: fast-1
PASS: Intel: full-width writes: rdpmc: cntr-2
SKIP: Intel: full-width writes: rdpmc: fast-2
PASS: Intel: full-width writes: rdpmc: cntr-3
SKIP: Intel: full-width writes: rdpmc: fast-3
PASS: Intel: full-width writes: rdpmc: fixed cntr-0
SKIP: Intel: full-width writes: rdpmc: fixed fast-0
PASS: Intel: full-width writes: rdpmc: fixed cntr-1
SKIP: Intel: full-width writes: rdpmc: fixed fast-1
PASS: Intel: full-width writes: rdpmc: fixed cntr-2
SKIP: Intel: full-width writes: rdpmc: fixed fast-2
PASS: Intel: full-width writes: all counters
FAIL: Intel: full-width writes: overflow: cntr-0
FAIL: Intel: full-width writes: overflow: status-0
PASS: Intel: full-width writes: overflow: status clear-0
PASS: Intel: full-width writes: overflow: irq-0
FAIL: Intel: full-width writes: overflow: cntr-1
FAIL: Intel: full-width writes: overflow: status-1
PASS: Intel: full-width writes: overflow: status clear-1
FAIL: Intel: full-width writes: overflow: irq-1
FAIL: Intel: full-width writes: overflow: cntr-2
FAIL: Intel: full-width writes: overflow: status-2
PASS: Intel: full-width writes: overflow: status clear-2
PASS: Intel: full-width writes: overflow: irq-2
FAIL: Intel: full-width writes: overflow: cntr-3
FAIL: Intel: full-width writes: overflow: status-3
PASS: Intel: full-width writes: overflow: status clear-3
FAIL: Intel: full-width writes: overflow: irq-3
FAIL: Intel: full-width writes: overflow: cntr-4
FAIL: Intel: full-width writes: overflow: status-4
PASS: Intel: full-width writes: overflow: status clear-4
PASS: Intel: full-width writes: overflow: irq-4
PASS: Intel: full-width writes: cmask
PASS: Intel: full-width writes: running counter wrmsr: cntr
PASS: Intel: full-width writes: running counter wrmsr: status msr bit
PASS: Intel: full-width writes: writing unsupported width to MSR_IA32_PMC0 raises #GP
PASS: Intel: full-width writes: writing unsupported width to MSR_IA32_PMC1 raises #GP
PASS: Intel: full-width writes: writing unsupported width to MSR_IA32_PMC2 raises #GP
PASS: Intel: full-width writes: writing unsupported width to MSR_IA32_PMC3 raises #GP
SUMMARY: 143 tests, 24 unexpected failures, 14 skipped


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [linus:master] [perf/x86/intel] 25dfc9e357: kvm-unit-tests-qemu.pmu.fail
  2024-09-23  4:31   ` Oliver Sang
@ 2024-09-24  2:17     ` Mi, Dapeng
  2024-09-24  2:46       ` Oliver Sang
  0 siblings, 1 reply; 7+ messages in thread
From: Mi, Dapeng @ 2024-09-24  2:17 UTC (permalink / raw)
  To: Oliver Sang, Liang, Kan
  Cc: oe-lkp, lkp, linux-kernel, Thomas Gleixner, Li Huafei,
	linux-perf-users


On 9/23/2024 12:31 PM, Oliver Sang wrote:
> hi, Kan,
>
> On Fri, Sep 20, 2024 at 09:27:06AM -0400, Liang, Kan wrote:
>
>>> ...
>>> ^[[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?
> I attached a pmu.log.
>
> below failed which can pass on parent (v6.11-rc5)
>
> FAIL: Intel: overflow: cntr-0
> FAIL: Intel: overflow: status-0
> FAIL: Intel: overflow: cntr-1
> FAIL: Intel: overflow: status-1
> FAIL: Intel: overflow: irq-1
> FAIL: Intel: overflow: cntr-2
> FAIL: Intel: overflow: status-2
> FAIL: Intel: overflow: cntr-3
> FAIL: Intel: overflow: status-3
> FAIL: Intel: overflow: irq-3
> FAIL: Intel: overflow: cntr-4
> FAIL: Intel: overflow: status-4
> FAIL: Intel: full-width writes: overflow: cntr-0
> FAIL: Intel: full-width writes: overflow: status-0
> FAIL: Intel: full-width writes: overflow: cntr-1
> FAIL: Intel: full-width writes: overflow: status-1
> FAIL: Intel: full-width writes: overflow: irq-1
> FAIL: Intel: full-width writes: overflow: cntr-2
> FAIL: Intel: full-width writes: overflow: status-2
> FAIL: Intel: full-width writes: overflow: cntr-3
> FAIL: Intel: full-width writes: overflow: status-3
> FAIL: Intel: full-width writes: overflow: irq-3
> FAIL: Intel: full-width writes: overflow: cntr-4
> FAIL: Intel: full-width writes: overflow: status-4

Hi Oliver,

What HW platform do you see this error on? If possible, could you please
apply the previously mentioned KUT/pmu patchset and check if the issue can
be fixed? Thanks.

Dapeng Mi

>
>
>> 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
>>>
>>>
>>>

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [linus:master] [perf/x86/intel] 25dfc9e357: kvm-unit-tests-qemu.pmu.fail
  2024-09-24  2:17     ` Mi, Dapeng
@ 2024-09-24  2:46       ` Oliver Sang
  2024-09-24  3:16         ` Mi, Dapeng
  0 siblings, 1 reply; 7+ messages in thread
From: Oliver Sang @ 2024-09-24  2:46 UTC (permalink / raw)
  To: Mi, Dapeng
  Cc: Liang, Kan, oe-lkp, lkp, linux-kernel, Thomas Gleixner, Li Huafei,
	linux-perf-users, oliver.sang

hi, Dapeng Mi,

On Tue, Sep 24, 2024 at 10:17:17AM +0800, Mi, Dapeng wrote:
> 
> On 9/23/2024 12:31 PM, Oliver Sang wrote:
> > hi, Kan,
> >
> > On Fri, Sep 20, 2024 at 09:27:06AM -0400, Liang, Kan wrote:
> >
> >>> ...
> >>> ^[[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?
> > I attached a pmu.log.
> >
> > below failed which can pass on parent (v6.11-rc5)
> >
> > FAIL: Intel: overflow: cntr-0
> > FAIL: Intel: overflow: status-0
> > FAIL: Intel: overflow: cntr-1
> > FAIL: Intel: overflow: status-1
> > FAIL: Intel: overflow: irq-1
> > FAIL: Intel: overflow: cntr-2
> > FAIL: Intel: overflow: status-2
> > FAIL: Intel: overflow: cntr-3
> > FAIL: Intel: overflow: status-3
> > FAIL: Intel: overflow: irq-3
> > FAIL: Intel: overflow: cntr-4
> > FAIL: Intel: overflow: status-4
> > FAIL: Intel: full-width writes: overflow: cntr-0
> > FAIL: Intel: full-width writes: overflow: status-0
> > FAIL: Intel: full-width writes: overflow: cntr-1
> > FAIL: Intel: full-width writes: overflow: status-1
> > FAIL: Intel: full-width writes: overflow: irq-1
> > FAIL: Intel: full-width writes: overflow: cntr-2
> > FAIL: Intel: full-width writes: overflow: status-2
> > FAIL: Intel: full-width writes: overflow: cntr-3
> > FAIL: Intel: full-width writes: overflow: status-3
> > FAIL: Intel: full-width writes: overflow: irq-3
> > FAIL: Intel: full-width writes: overflow: cntr-4
> > FAIL: Intel: full-width writes: overflow: status-4
> 
> Hi Oliver,
> 
> What HW platform do you see this error on? 

it's on a Haswell desktop
test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (Haswell) with 16G memory

> If possible, could you please
> apply the previously mentioned KUT/pmu patchset and check if the issue can
> be fixed? Thanks.

do you have a repo/branch? unfortunately, our bot failed to fetch this
patch-set.

> 
> Dapeng Mi
> 
> >
> >
> >> 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
> >>>
> >>>
> >>>
> 

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [linus:master] [perf/x86/intel] 25dfc9e357: kvm-unit-tests-qemu.pmu.fail
  2024-09-24  2:46       ` Oliver Sang
@ 2024-09-24  3:16         ` Mi, Dapeng
  0 siblings, 0 replies; 7+ messages in thread
From: Mi, Dapeng @ 2024-09-24  3:16 UTC (permalink / raw)
  To: Oliver Sang
  Cc: Liang, Kan, oe-lkp, lkp, linux-kernel, Thomas Gleixner, Li Huafei,
	linux-perf-users


On 9/24/2024 10:46 AM, Oliver Sang wrote:
> hi, Dapeng Mi,
>
> On Tue, Sep 24, 2024 at 10:17:17AM +0800, Mi, Dapeng wrote:
>> On 9/23/2024 12:31 PM, Oliver Sang wrote:
>>> hi, Kan,
>>>
>>> On Fri, Sep 20, 2024 at 09:27:06AM -0400, Liang, Kan wrote:
>>>
>>>>> ...
>>>>> ^[[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?
>>> I attached a pmu.log.
>>>
>>> below failed which can pass on parent (v6.11-rc5)
>>>
>>> FAIL: Intel: overflow: cntr-0
>>> FAIL: Intel: overflow: status-0
>>> FAIL: Intel: overflow: cntr-1
>>> FAIL: Intel: overflow: status-1
>>> FAIL: Intel: overflow: irq-1
>>> FAIL: Intel: overflow: cntr-2
>>> FAIL: Intel: overflow: status-2
>>> FAIL: Intel: overflow: cntr-3
>>> FAIL: Intel: overflow: status-3
>>> FAIL: Intel: overflow: irq-3
>>> FAIL: Intel: overflow: cntr-4
>>> FAIL: Intel: overflow: status-4
>>> FAIL: Intel: full-width writes: overflow: cntr-0
>>> FAIL: Intel: full-width writes: overflow: status-0
>>> FAIL: Intel: full-width writes: overflow: cntr-1
>>> FAIL: Intel: full-width writes: overflow: status-1
>>> FAIL: Intel: full-width writes: overflow: irq-1
>>> FAIL: Intel: full-width writes: overflow: cntr-2
>>> FAIL: Intel: full-width writes: overflow: status-2
>>> FAIL: Intel: full-width writes: overflow: cntr-3
>>> FAIL: Intel: full-width writes: overflow: status-3
>>> FAIL: Intel: full-width writes: overflow: irq-3
>>> FAIL: Intel: full-width writes: overflow: cntr-4
>>> FAIL: Intel: full-width writes: overflow: status-4
>> Hi Oliver,
>>
>> What HW platform do you see this error on? 
> it's on a Haswell desktop
> test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (Haswell) with 16G memory
>
>> If possible, could you please
>> apply the previously mentioned KUT/pmu patchset and check if the issue can
>> be fixed? Thanks.
> do you have a repo/branch? unfortunately, our bot failed to fetch this
> patch-set.

Please try this branch.
https://github.com/intel-sandbox/dapengmi-kvm-unit-tests/commits/main/


>
>> Dapeng Mi
>>
>>>
>>>> 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
>>>>>
>>>>>
>>>>>

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2024-09-24  3:16 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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

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).