From: Mingwei Zhang <mizhang@google.com>
To: Dapeng Mi <dapeng1.mi@linux.intel.com>
Cc: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Zhenyu Wang <zhenyuw@linux.intel.com>,
Zhang Xiong <xiong.y.zhang@intel.com>,
Jim Mattson <jmattson@google.com>,
Like Xu <like.xu.linux@gmail.com>,
Dapeng Mi <dapeng1.mi@intel.com>
Subject: Re: [kvm-unit-tests Patch 0/5] Fix PMU test failures on Sapphire Rapids
Date: Wed, 25 Oct 2023 23:47:00 +0000 [thread overview]
Message-ID: <ZTmo9IVM2Tq6ZSrn@google.com> (raw)
In-Reply-To: <20231024075748.1675382-1-dapeng1.mi@linux.intel.com>
On Tue, Oct 24, 2023, Dapeng Mi wrote:
> When running pmu test on Intel Sapphire Rapids, we found several
> failures are encountered, such as "llc misses" failure, "all counters"
> failure and "fixed counter 3" failure.
hmm, I have tested your series on a SPR machine. It looks like, all "llc
misses" already pass on my side. "all counters" always fail with/without
your patches. "fixed counter 3" never exists... I have "fixed
cntr-{0,1,2}" and "fixed-{0,1,2}"
You may want to double check the requirements of your series. Not just
under your setting without explainning those setting in detail.
Maybe what I am missing is your topdown series? So, before your topdown
series checked in. I don't see value in this series.
Thanks.
-Mingwei
>
> Intel Sapphire Rapids introduces new fixed counter 3, total PMU counters
> including GP and fixed counters increase to 12 and also optimizes cache
> subsystem. All these changes make the original assumptions in pmu test
> unavailable any more on Sapphire Rapids. Patches 2-4 fixes these
> failures, patch 0 remove the duplicate code and patch 5 adds assert to
> ensure predefine fixed events are matched with HW fixed counters.
>
> Dapeng Mi (4):
> x86: pmu: Change the minimum value of llc_misses event to 0
> x86: pmu: Enlarge cnt array length to 64 in check_counters_many()
> x86: pmu: Support validation for Intel PMU fixed counter 3
> x86: pmu: Add asserts to warn inconsistent fixed events and counters
>
> Xiong Zhang (1):
> x86: pmu: Remove duplicate code in pmu_init()
>
> lib/x86/pmu.c | 5 -----
> x86/pmu.c | 17 ++++++++++++-----
> 2 files changed, 12 insertions(+), 10 deletions(-)
>
>
> base-commit: bfe5d7d0e14c8199d134df84d6ae8487a9772c48
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-10-25 23:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 7:57 [kvm-unit-tests Patch 0/5] Fix PMU test failures on Sapphire Rapids Dapeng Mi
2023-10-24 7:57 ` [kvm-unit-tests Patch 1/5] x86: pmu: Remove duplicate code in pmu_init() Dapeng Mi
2023-10-24 7:57 ` [kvm-unit-tests Patch 2/5] x86: pmu: Change the minimum value of llc_misses event to 0 Dapeng Mi
2023-10-24 13:03 ` Jim Mattson
2023-10-25 11:22 ` Mi, Dapeng
2023-10-25 12:35 ` Jim Mattson
2023-10-26 2:14 ` Mi, Dapeng
2023-10-26 12:19 ` Jim Mattson
2023-10-27 10:17 ` Mi, Dapeng
2023-10-24 7:57 ` [kvm-unit-tests Patch 3/5] x86: pmu: Enlarge cnt array length to 64 in check_counters_many() Dapeng Mi
2023-10-24 7:57 ` [kvm-unit-tests Patch 4/5] x86: pmu: Support validation for Intel PMU fixed counter 3 Dapeng Mi
2023-10-24 19:05 ` Jim Mattson
2023-10-25 11:26 ` Mi, Dapeng
2023-10-25 12:38 ` Jim Mattson
2023-10-26 2:29 ` Mi, Dapeng
2023-10-24 7:57 ` [kvm-unit-tests Patch 5/5] x86: pmu: Add asserts to warn inconsistent fixed events and counters Dapeng Mi
2023-10-25 23:47 ` Mingwei Zhang [this message]
2023-10-26 3:32 ` [kvm-unit-tests Patch 0/5] Fix PMU test failures on Sapphire Rapids Mi, Dapeng
2023-10-30 3:57 ` Mingwei Zhang
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=ZTmo9IVM2Tq6ZSrn@google.com \
--to=mizhang@google.com \
--cc=dapeng1.mi@intel.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=like.xu.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=xiong.y.zhang@intel.com \
--cc=zhenyuw@linux.intel.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