linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
To: Oliver Sang <oliver.sang@intel.com>,
	"Liang, Kan" <kan.liang@linux.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: Tue, 24 Sep 2024 10:17:17 +0800	[thread overview]
Message-ID: <196706e4-e892-4e73-8ba7-1fa939d8998b@linux.intel.com> (raw)
In-Reply-To: <ZvDvB98DW10Au8lo@xsang-OptiPlex-9020>


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

  reply	other threads:[~2024-09-24  2:17 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
2024-09-23  4:31   ` Oliver Sang
2024-09-24  2:17     ` Mi, Dapeng [this message]
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=196706e4-e892-4e73-8ba7-1fa939d8998b@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 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).