public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Dapeng Mi <dapeng1.mi@linux.intel.com>
To: Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jim Mattson <jmattson@google.com>,
	Mingwei Zhang <mizhang@google.com>,
	Xiong Zhang <xiong.y.zhang@intel.com>,
	Zhenyu Wang <zhenyuw@linux.intel.com>,
	Like Xu <like.xu.linux@gmail.com>,
	Jinrong Liang <cloudliang@tencent.com>,
	Dapeng Mi <dapeng1.mi@intel.com>,
	Dapeng Mi <dapeng1.mi@linux.intel.com>
Subject: [Patch v5 00/18] pmu test bugs fix and improvements
Date: Wed,  3 Jul 2024 09:56:54 +0000	[thread overview]
Message-ID: <20240703095712.64202-1-dapeng1.mi@linux.intel.com> (raw)

Changes:
v4 -> v5:
  * Fix the building errors with configuration options "--arch=i386" or
    "--enable-efi' introduced by v4 patch "Add IBPB indirect jump asm 
    blob" (Patch 15/18)
  * Add patch 18/18 to print count details if test case fails


All changes pass validation on Intel Sapphire Rapids and Emerald Rapids
platforms against latest kvm-x86/next code (0ce958282e66). No tests on
AMD platforms since no AMD platform on hand. Any tests on AMD platform
are appreciated.

History:
  v4: https://lore.kernel.org/all/20240419035233.3837621-1-dapeng1.mi@linux.intel.com/
  v3: https://lore.kernel.org/lkml/20240103031409.2504051-1-dapeng1.mi@linux.intel.com/ 
  v2: https://lore.kernel.org/lkml/20231031092921.2885109-1-dapeng1.mi@linux.intel.com/
  v1: https://lore.kernel.org/lkml/20231024075748.1675382-1-dapeng1.mi@linux.intel.com/

Dapeng Mi (17):
  x86: pmu: Remove blank line and redundant space
  x86: pmu: Refine fixed_events[] names
  x86: pmu: Fix the issue that pmu_counter_t.config crosses cache line
  x86: pmu: Enlarge cnt[] length to 48 in check_counters_many()
  x86: pmu: Add asserts to warn inconsistent fixed events and counters
  x86: pmu: Fix cycles event validation failure
  x86: pmu: Use macro to replace hard-coded branches event index
  x86: pmu: Use macro to replace hard-coded ref-cycles event index
  x86: pmu: Use macro to replace hard-coded instructions event index
  x86: pmu: Enable and disable PMCs in loop() asm blob
  x86: pmu: Improve instruction and branches events verification
  x86: pmu: Improve LLC misses event verification
  x86: pmu: Adjust lower boundary of llc-misses event to 0 for legacy
    CPUs
  x86: pmu: Add IBPB indirect jump asm blob
  x86: pmu: Adjust lower boundary of branch-misses event
  x86: pmu: Optimize emulated instruction validation
  x86: pmu: Print measured event count if test fails

Xiong Zhang (1):
  x86: pmu: Remove duplicate code in pmu_init()

 lib/x86/pmu.c |   5 -
 x86/pmu.c     | 406 ++++++++++++++++++++++++++++++++++++++++----------
 2 files changed, 328 insertions(+), 83 deletions(-)


base-commit: d301d0187f5db09531a1c2c7608997cc3b0a5c7d
-- 
2.40.1


             reply	other threads:[~2024-07-03  2:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-03  9:56 Dapeng Mi [this message]
2024-07-03  9:56 ` [Patch v5 01/18] x86: pmu: Remove duplicate code in pmu_init() Dapeng Mi
2024-07-03  9:56 ` [Patch v5 02/18] x86: pmu: Remove blank line and redundant space Dapeng Mi
2024-07-03  9:56 ` [Patch v5 03/18] x86: pmu: Refine fixed_events[] names Dapeng Mi
2024-07-03  9:56 ` [Patch v5 04/18] x86: pmu: Fix the issue that pmu_counter_t.config crosses cache line Dapeng Mi
2024-07-03  9:56 ` [Patch v5 05/18] x86: pmu: Enlarge cnt[] length to 48 in check_counters_many() Dapeng Mi
2024-07-03  9:57 ` [Patch v5 06/18] x86: pmu: Add asserts to warn inconsistent fixed events and counters Dapeng Mi
2024-08-22 18:22   ` Jim Mattson
2024-08-26  6:56     ` Mi, Dapeng
2024-08-26 18:36       ` Jim Mattson
2024-08-27  0:41         ` Mi, Dapeng
2024-07-03  9:57 ` [Patch v5 07/18] x86: pmu: Fix cycles event validation failure Dapeng Mi
2024-07-03  9:57 ` [Patch v5 08/18] x86: pmu: Use macro to replace hard-coded branches event index Dapeng Mi
2024-07-03  9:57 ` [Patch v5 09/18] x86: pmu: Use macro to replace hard-coded ref-cycles " Dapeng Mi
2024-07-03  9:57 ` [Patch v5 10/18] x86: pmu: Use macro to replace hard-coded instructions " Dapeng Mi
2024-07-03  9:57 ` [Patch v5 11/18] x86: pmu: Enable and disable PMCs in loop() asm blob Dapeng Mi
2024-07-03  9:57 ` [Patch v5 12/18] x86: pmu: Improve instruction and branches events verification Dapeng Mi
2024-07-04  8:02   ` Sandipan Das
2024-07-04 12:21     ` Mi, Dapeng
2024-07-03  9:57 ` [Patch v5 13/18] x86: pmu: Improve LLC misses event verification Dapeng Mi
2024-07-03  9:57 ` [Patch v5 14/18] x86: pmu: Adjust lower boundary of llc-misses event to 0 for legacy CPUs Dapeng Mi
2024-07-03  9:57 ` [Patch v5 15/18] x86: pmu: Add IBPB indirect jump asm blob Dapeng Mi
2024-07-03  9:57 ` [Patch v5 16/18] x86: pmu: Adjust lower boundary of branch-misses event Dapeng Mi
2024-07-03  9:57 ` [Patch v5 17/18] x86: pmu: Optimize emulated instruction validation Dapeng Mi
2024-07-03  9:57 ` [Patch v5 18/18] x86: pmu: Print measured event count if test fails Dapeng Mi

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=20240703095712.64202-1-dapeng1.mi@linux.intel.com \
    --to=dapeng1.mi@linux.intel.com \
    --cc=cloudliang@tencent.com \
    --cc=dapeng1.mi@intel.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=like.xu.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mizhang@google.com \
    --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