public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
To: Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, Like Xu <like.xu.linux@gmail.com>,
	Mingwei Zhang <mizhang@google.com>,
	Zhenyu Wang <zhenyuw@linux.intel.com>,
	Zhang Xiong <xiong.y.zhang@intel.com>,
	Lv Zhiyuan <zhiyuan.lv@intel.com>,
	Dapeng Mi <dapeng1.mi@intel.com>
Subject: Re: [kvm-unit-tests PATCH 0/4] x86/pmu: PEBS fixes and new testcases
Date: Thu, 7 Mar 2024 17:22:09 +0800	[thread overview]
Message-ID: <b0eb5d58-efbd-4f4a-98d6-d470b242c238@linux.intel.com> (raw)
In-Reply-To: <20240306230153.786365-1-seanjc@google.com>


On 3/7/2024 7:01 AM, Sean Christopherson wrote:
> One bug fix where pmu_pebs attempts to enable PEBS for fixed counter on
> CPUs without Extended PEBS, and two new testcases to verify adaptive
> PEBS functionality.
>
> The new testcases are intended both to demonstrate that adaptive PEBS
> virtualization is currently broken, and to serve as a gatekeeper for
> re-enabling adapative PEBS in the future.
>
> https://lore.kernel.org/all/ZeepGjHCeSfadANM@google.com
>
> Sean Christopherson (4):
>    x86/pmu: Enable PEBS on fixed counters iff baseline PEBS is support
>    x86/pmu: Iterate over adaptive PEBS flag combinations
>    x86/pmu: Test adaptive PEBS without any adaptive counters
>    x86/pmu: Add a PEBS test to verify the host LBRs aren't leaked to the
>      guest
>
>   lib/x86/pmu.h  |   6 ++-
>   x86/pmu_pebs.c | 109 +++++++++++++++++++++++++++----------------------
>   2 files changed, 66 insertions(+), 49 deletions(-)

Tested-by: Dapeng Mi <dapeng1.mi@linux.intel.com>

>
> base-commit: 55dd01b4f066577b49f03fb7146723c4a65822c4

  parent reply	other threads:[~2024-03-07  9:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 23:01 [kvm-unit-tests PATCH 0/4] x86/pmu: PEBS fixes and new testcases Sean Christopherson
2024-03-06 23:01 ` [kvm-unit-tests PATCH 1/4] x86/pmu: Enable PEBS on fixed counters iff baseline PEBS is support Sean Christopherson
2024-03-07  9:22   ` Mi, Dapeng
2024-03-06 23:01 ` [kvm-unit-tests PATCH 2/4] x86/pmu: Iterate over adaptive PEBS flag combinations Sean Christopherson
2024-03-06 23:01 ` [kvm-unit-tests PATCH 3/4] x86/pmu: Test adaptive PEBS without any adaptive counters Sean Christopherson
2024-03-07  9:08   ` Like Xu
2024-03-07  9:28   ` Mi, Dapeng
2024-06-05 16:17     ` Sean Christopherson
2024-03-07 10:00   ` Mi, Dapeng
2024-03-06 23:01 ` [kvm-unit-tests PATCH 4/4] x86/pmu: Add a PEBS test to verify the host LBRs aren't leaked to the guest Sean Christopherson
2024-03-07  9:23   ` Like Xu
2024-03-07  9:31   ` Mi, Dapeng
2024-03-07  9:22 ` Mi, Dapeng [this message]
2024-06-05 23:20 ` [kvm-unit-tests PATCH 0/4] x86/pmu: PEBS fixes and new testcases Sean Christopherson
2024-06-06  0:51   ` Mi, Dapeng1

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=b0eb5d58-efbd-4f4a-98d6-d470b242c238@linux.intel.com \
    --to=dapeng1.mi@linux.intel.com \
    --cc=dapeng1.mi@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=like.xu.linux@gmail.com \
    --cc=mizhang@google.com \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=xiong.y.zhang@intel.com \
    --cc=zhenyuw@linux.intel.com \
    --cc=zhiyuan.lv@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