mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chen, Zide" <zide.chen@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jim Mattson <jmattson@google.com>,
	Mingwei Zhang <mizhang@google.com>,
	Das Sandipan <Sandipan.Das@amd.com>,
	Shukla Manali <Manali.Shukla@amd.com>,
	Dapeng Mi <dapeng1.mi@linux.intel.com>,
	Falcon Thomas <thomas.falcon@intel.com>,
	Xudong Hao <xudong.hao@intel.com>
Subject: Re: [PATCH V2 0/4] KVM: x86/pmu: Add hardware Topdown metrics support
Date: Fri, 12 Jun 2026 14:08:07 -0500	[thread overview]
Message-ID: <caa29b0f-3c44-4c37-baf7-64873123a8dd@intel.com> (raw)
In-Reply-To: <ainfKdOgKp9i2qDP@google.com>



On 6/10/2026 5:03 PM, Sean Christopherson wrote:
> On Thu, Apr 23, 2026, Zide Chen wrote:
>> The Top-Down Microarchitecture Analysis (TMA) method is a structured
>> approach for identifying performance bottlenecks in out-of-order
>> processors.
>>
>> Currently, guests support the TMA method by collecting Topdown events
>> using GP counters, which may trigger multiplexing.  To free up scarce
>> GP counters, eliminate multiplexing-induced skew, and obtain coherent
>> Topdown metric ratios, it is desirable to expose fixed counter 3 and
>> the IA32_PERF_METRICS MSR to guests.
>>
>> Several attempts have been made to virtualize this under the legacy
>> vPMU model [1][2][3], but they were unsuccessful.  With the new mediated
>> vPMU, enabling TMA support in guests becomes much simpler.  It avoids
>> invasive changes to the perf core, eliminates CPU pinning and
>> fixed-counter affinity issues, and reduces the latge overhead of
>> trapping and emulating MSR accesses.
> 
> Please submit a new version of this to address Dapeng's feedback, rebase on the
> latest kvm-x86/next, and perhaps most importantly, to let Sashiko take a crack
> at it.

Yes, will submit V3 in coming days.
> Thanks!


      reply	other threads:[~2026-06-12 19:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23 17:46 Zide Chen
2026-04-23 17:46 ` [PATCH V2 1/4] KVM: x86/pmu: Do not map fixed counters >= 3 to generic perf events Zide Chen
2026-04-30  1:55   ` Mi, Dapeng
2026-04-23 17:46 ` [PATCH V2 2/4] KVM: x86/pmu: Support Intel fixed counter 3 on mediated vPMU Zide Chen
2026-04-30  2:19   ` Mi, Dapeng
2026-04-30 17:54     ` Chen, Zide
2026-05-06  1:36       ` Mi, Dapeng
2026-04-23 17:46 ` [PATCH V2 3/4] KVM: x86/pmu: Support PERF_METRICS MSR in " Zide Chen
2026-04-30  2:22   ` Mi, Dapeng
2026-04-23 17:46 ` [PATCH V2 4/4] KVM: selftests: Add perf_metrics and fixed counter 3 tests Zide Chen
2026-04-30  2:26   ` Mi, Dapeng
2026-04-30 18:13     ` Chen, Zide
2026-06-10 22:03 ` [PATCH V2 0/4] KVM: x86/pmu: Add hardware Topdown metrics support Sean Christopherson
2026-06-12 19:08   ` Chen, Zide [this message]

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=caa29b0f-3c44-4c37-baf7-64873123a8dd@intel.com \
    --to=zide.chen@intel.com \
    --cc=Manali.Shukla@amd.com \
    --cc=Sandipan.Das@amd.com \
    --cc=dapeng1.mi@linux.intel.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mizhang@google.com \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=thomas.falcon@intel.com \
    --cc=xudong.hao@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

all inboxes | Powered by JetHome®