Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
To: "Chen, Zide" <zide.chen@intel.com>,
	Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: kvm@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
	Jim Mattson <jmattson@google.com>,
	Stephane Eranian <eranian@google.com>,
	linux-kernel@vger.kernel.org, Mingwei Zhang <mizhang@google.com>,
	Das Sandipan <Sandipan.Das@amd.com>,
	Shukla Manali <Manali.Shukla@amd.com>,
	Xudong Hao <xudong.hao@intel.com>
Subject: Re: [PATCH v2 11/16] KVM: x86/pmu: Emulate the GLOBAL_STATUS_SET and GLOBAL_INUSE MSRs
Date: Wed, 2 Sep 2026 08:44:20 +0800	[thread overview]
Message-ID: <1c097f89-18ac-4d41-85fc-8660cb6603f4@linux.intel.com> (raw)
In-Reply-To: <8e9aeb61-30fc-4a1a-8a6d-9104f9ebdd6f@intel.com>


On 9/1/2026 10:20 PM, Chen, Zide wrote:
>
> On 9/1/2026 1:45 AM, Mi, Dapeng wrote:
>> On 8/28/2026 6:37 AM, Zide Chen wrote:
>>> Intel PerfMon v4 introduces IA32_PERF_GLOBAL_STATUS_SET (0x391) to
>>> allow software to set individual bits in the global status MSR. Reads
>>> of IA32_PERF_GLOBAL_STATUS_SET always return zero.
>>>
>>> IA32_PERF_GLOBAL_INUSE (0x392) is also introduced in v4, to track
>>> which counters and the PMI are currently claimed by other agents,
>>> allowing independent software agents to check counter availability
>>> without a shared scheduler arbitrating between them.
>>>
>>> IA32_PERF_GLOBAL_INUSE is an read-only MSR, and any write attempt
>>> results in a #GP.
>>>
>>> Neither MSR is part of the VM state, so they don't need to be
>>> advertised to userspace, nor saved and restored during live
>>> migration.
>>>
>>> Originally-by: Yang Weijiang <weijiang.yang@intel.com>
>>> Signed-off-by: Zide Chen <zide.chen@intel.com>
>>> ---
>>> v2:
>>> - Change intel_pmu_get_global_inuse() to return u64, to match the
>>>   surrounding code style.
>>> - Add the missing vmcs02 updates for these two MSRs.
>>> - Change "> 3" to ">= 4" to make the "v4-gated" more obvious and match
>>>   the existing code style.
>>> ---
>>>  arch/x86/include/asm/msr-index.h |  4 ++++
>>>  arch/x86/kvm/pmu.c               |  9 ++++++++
>>>  arch/x86/kvm/vmx/nested.c        |  2 ++
>>>  arch/x86/kvm/vmx/pmu_intel.c     | 37 ++++++++++++++++++++++++++++++++
>>>  arch/x86/kvm/vmx/vmx.c           |  4 ++++
>>>  5 files changed, 56 insertions(+)
>>>
>>> diff --git a/arch/x86/include/asm/msr-index.h b/arch/x86/include/asm/msr-index.h
>>> index 11b99d237e05..0b093cf41edf 100644
>>> --- a/arch/x86/include/asm/msr-index.h
>>> +++ b/arch/x86/include/asm/msr-index.h
>>> @@ -1240,6 +1240,10 @@
>>>  #define MSR_CORE_PERF_GLOBAL_CTRL	0x0000038f
>>>  #define MSR_CORE_PERF_GLOBAL_OVF_CTRL	0x00000390
>>>  #define MSR_CORE_PERF_GLOBAL_STATUS_SET	0x00000391
>>> +#define MSR_CORE_PERF_GLOBAL_INUSE	0x00000392
>>> +
>>> +/* Intel IA32_PERF_GLOBAL_INUSE MSR */
>>> +#define PERF_GLOBAL_INUSE_PMI_INUSE	BIT_ULL(63)
>>>  
>>>  #define MSR_PERF_METRICS		0x00000329
>>>  
>>> diff --git a/arch/x86/kvm/pmu.c b/arch/x86/kvm/pmu.c
>>> index 437a7bc49bf8..7c05cf5157bf 100644
>>> --- a/arch/x86/kvm/pmu.c
>>> +++ b/arch/x86/kvm/pmu.c
>>> @@ -832,6 +832,8 @@ bool kvm_pmu_is_valid_msr(struct kvm_vcpu *vcpu, u32 msr)
>>>  	case MSR_CORE_PERF_GLOBAL_CTRL:
>>>  	case MSR_CORE_PERF_GLOBAL_OVF_CTRL:
>>>  		return kvm_pmu_has_perf_global_ctrl(vcpu_to_pmu(vcpu));
>>> +	case MSR_CORE_PERF_GLOBAL_STATUS_SET:
>>> +		return vcpu_to_pmu(vcpu)->version >= 4;
>>>  	default:
>>>  		break;
>>>  	}
>>> @@ -865,6 +867,7 @@ int kvm_pmu_get_msr(struct kvm_vcpu *vcpu, struct msr_data *msr_info)
>>>  	case MSR_AMD64_PERF_CNTR_GLOBAL_STATUS_CLR:
>>>  	case MSR_AMD64_PERF_CNTR_GLOBAL_STATUS_SET:
>>>  	case MSR_CORE_PERF_GLOBAL_OVF_CTRL:
>>> +	case MSR_CORE_PERF_GLOBAL_STATUS_SET:
>>>  		msr_info->data = 0;
>>>  		break;
>>>  	default:
>>> @@ -931,6 +934,12 @@ int kvm_pmu_set_msr(struct kvm_vcpu *vcpu, struct msr_data *msr_info)
>>>  		if (!msr_info->host_initiated)
>>>  			pmu->global_status &= ~data;
>>>  		break;
>>> +	case MSR_CORE_PERF_GLOBAL_STATUS_SET:
>>> +		if (data & pmu->global_status_rsvd)
>>> +			return 1;
>>> +		if (!msr_info->host_initiated)
>>> +			pmu->global_status |= data;
>>> +		break;
>>>  	case MSR_AMD64_PERF_CNTR_GLOBAL_STATUS_SET:
>>>  		if (!msr_info->host_initiated)
>>>  			pmu->global_status |= data & ~pmu->global_status_rsvd;
>>> diff --git a/arch/x86/kvm/vmx/nested.c b/arch/x86/kvm/vmx/nested.c
>>> index 0cff369982ae..ae7dd3636e70 100644
>>> --- a/arch/x86/kvm/vmx/nested.c
>>> +++ b/arch/x86/kvm/vmx/nested.c
>>> @@ -719,6 +719,8 @@ static void nested_vmx_merge_pmu_msr_bitmaps(struct kvm_vcpu *vcpu,
>>>  	nested_vmx_merge_msr_bitmaps_rw(MSR_CORE_PERF_GLOBAL_CTRL);
>>>  	nested_vmx_merge_msr_bitmaps_read(MSR_CORE_PERF_GLOBAL_STATUS);
>>>  	nested_vmx_merge_msr_bitmaps_write(MSR_CORE_PERF_GLOBAL_OVF_CTRL);
>>> +	nested_vmx_merge_msr_bitmaps_write(MSR_CORE_PERF_GLOBAL_STATUS_SET);
>>> +	nested_vmx_merge_msr_bitmaps_read(MSR_CORE_PERF_GLOBAL_INUSE);
>>>  }
>>>  
>>>  /*
>>> diff --git a/arch/x86/kvm/vmx/pmu_intel.c b/arch/x86/kvm/vmx/pmu_intel.c
>>> index 4df55a3e21da..3070fba2687f 100644
>>> --- a/arch/x86/kvm/vmx/pmu_intel.c
>>> +++ b/arch/x86/kvm/vmx/pmu_intel.c
>>> @@ -194,6 +194,8 @@ static bool intel_is_valid_msr(struct kvm_vcpu *vcpu, u32 msr)
>>>  	switch (msr) {
>>>  	case MSR_CORE_PERF_FIXED_CTR_CTRL:
>>>  		return kvm_pmu_has_perf_global_ctrl(pmu);
>>> +	case MSR_CORE_PERF_GLOBAL_INUSE:
>>> +		return pmu->version >= 4;
>>>  	case MSR_IA32_PEBS_ENABLE:
>>>  		ret = vcpu_get_perf_capabilities(vcpu) & PERF_CAP_PEBS_FORMAT;
>>>  		break;
>>> @@ -341,6 +343,38 @@ static bool intel_pmu_handle_lbr_msrs_access(struct kvm_vcpu *vcpu,
>>>  	return true;
>>>  }
>>>  
>>> +static u64 intel_pmu_get_global_inuse(struct kvm_vcpu *vcpu)
>>> +{
>>> +	struct kvm_pmu *pmu = vcpu_to_pmu(vcpu);
>>> +	unsigned long fixed_mask = kvm_fixed_pmc_mask(pmu);
>>> +	unsigned long gp_mask = kvm_gp_pmc_mask(pmu);
>>> +	bool pmi_inuse = false;
>>> +	u64 eventsel, data = 0;
>>> +	u32 fixed_ctrl;
>>> +	int i;
>>> +
>>> +	kvm_for_each_gp_counter(i, gp_mask) {
>>> +		eventsel = pmu->gp_counters[i].eventsel;
>>> +
>>> +		if (eventsel & ARCH_PERFMON_EVENTSEL_EVENT)
>> Why to check ARCH_PERFMON_EVENTSEL_EVENT instead of
>> ARCH_PERFMON_EVENTSEL_ENABLE here? Suppose only
>> ARCH_PERFMON_EVENTSEL_ENABLE is set, then the counter is in use.
> This implementation strictly follows the SDM, which checks the event
> bits, not the enable bit. This is also verified on bare metal.
>
> "IA32_PERF_GLOBAL_INUSE.PERFEVTSEL0_InUse[bit 0]: This bit reflects the
> logical state of (IA32_PERFEVTSEL0[7:0] != 0)."

Ok, thanks for double checking. 


>
> That's why, in the reply above to Sashiko, I noted that on bare metal
> without a vCPU scheduled in, after a perf event is closed, the counter
> could still show as in use. perf/x86 clears the enable bit while keeps
> the event bits set.

That's why I feel confusing. Currently perf/x86 doesn't clear the Evensel
field and only clears the enable bit, so IN_USE bit would be set forever
once an event ever used the counter even the GP counter is not enabled
right now.

It's deserved to add a comment here, I believe some persons have same
question with me.

Anyway, let's keep consistent with SDM here. Thanks.



  reply	other threads:[~2026-09-02  0:44 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 22:37 [PATCH] KVM: x86/pmu: Add mediated vPMU PerfMon v5 support Zide Chen
2026-08-27 22:37 ` [PATCH v2 01/16] KVM: x86/pmu: Remove redundant Perf Global Status MSR bit definitions Zide Chen
2026-08-27 22:57   ` sashiko-bot
2026-08-28 13:51     ` Chen, Zide
2026-09-01  2:07   ` Mi, Dapeng
2026-08-27 22:37 ` [PATCH v2 02/16] KVM: x86/pmu: Rename all_valid_pmc_idx to pmc_exists Zide Chen
2026-09-01  2:09   ` Mi, Dapeng
2026-08-27 22:37 ` [PATCH v2 03/16] KVM: x86/pmu: Rename reserved_bits to eventsel_rsvd in kvm_pmu Zide Chen
2026-09-01  2:17   ` Mi, Dapeng
2026-08-27 22:37 ` [PATCH v2 04/16] KVM: x86/pmu: Gate BUFFER_OVF reserved bit on guest DS Zide Chen
2026-09-01  2:30   ` Mi, Dapeng
2026-08-27 22:37 ` [PATCH v2 05/16] KVM: x86/pmu: Add PMC bitmap accessor helpers Zide Chen
2026-09-01  2:43   ` Mi, Dapeng
2026-08-27 22:37 ` [PATCH v2 06/16] KVM: x86/pmu: Drop nr_arch_{gp,fixed}_counters from kvm_pmu Zide Chen
2026-09-01  3:07   ` Mi, Dapeng
2026-08-27 22:37 ` [PATCH v2 07/16] KVM: x86/pmu: Expose kvm_host_pmu to vendor modules Zide Chen
2026-09-01  3:08   ` Mi, Dapeng
2026-08-27 22:37 ` [PATCH v2 08/16] perf/x86: Plumb counter bitmap from x86_pmu to x86_pmu_cap Zide Chen
2026-08-27 22:37 ` [PATCH v2 09/16] KVM: x86/pmu: Switch to bitmask-based KVM PMU capabilities Zide Chen
2026-09-01  3:32   ` Mi, Dapeng
2026-08-27 22:37 ` [PATCH v2 10/16] perf/x86: Remove num_counters_{gp,fixed} from x86_pmu_capability Zide Chen
2026-08-27 22:37 ` [PATCH v2 11/16] KVM: x86/pmu: Emulate the GLOBAL_STATUS_SET and GLOBAL_INUSE MSRs Zide Chen
2026-08-27 23:05   ` sashiko-bot
2026-08-28 20:22     ` Chen, Zide
2026-09-01  6:45   ` Mi, Dapeng
2026-09-01 14:20     ` Chen, Zide
2026-09-02  0:44       ` Mi, Dapeng [this message]
2026-08-27 22:37 ` [PATCH v2 12/16] KVM: x86/pmu: Populate CPUID.0AH:ECX fixed-counter bitmap Zide Chen
2026-09-01  6:50   ` Mi, Dapeng
2026-08-27 22:37 ` [PATCH v2 13/16] KVM: x86/pmu: Factor out fixed counter control bit calculation Zide Chen
2026-09-01  6:57   ` Mi, Dapeng
2026-08-27 22:37 ` [PATCH v2 14/16] KVM: x86/pmu: Ignore AnyThread bit if CPUID.0AH:EDX[15] is set Zide Chen
2026-09-01  8:01   ` Mi, Dapeng
2026-08-27 22:37 ` [PATCH v2 15/16] KVM: x86/pmu: Advertise PerfMon version 5 on Intel hosts Zide Chen
2026-08-27 22:37 ` [PATCH v2 16/16] KVM: selftests: Support fixed counters bitmap in pmu_counters_test Zide Chen
2026-08-29  9:30 ` [PATCH] KVM: x86/pmu: Add mediated vPMU PerfMon v5 support Peter Zijlstra

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=1c097f89-18ac-4d41-85fc-8660cb6603f4@linux.intel.com \
    --to=dapeng1.mi@linux.intel.com \
    --cc=Manali.Shukla@amd.com \
    --cc=Sandipan.Das@amd.com \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.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=peterz@infradead.org \
    --cc=seanjc@google.com \
    --cc=xudong.hao@intel.com \
    --cc=zide.chen@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