Re: [PATCH v5 12/12] KVM/VMX/vPMU: support to report GLOBAL_STATUS_LBRS_FROZEN
On 02/15/2019 09:10 PM, Andi Kleen wrote: OK. The freeze bits need to be cleared by IA32_PERF_GLOBAL_STATUS_RESET, which seems not supported by the perf code yet (thus guest won't clear them). Would handle_irq_v4 also need to be changed to support that? In Arch Perfmon v4 it is cleared by the MSR_CORE_PERF_GLOBAL_OVF_CTRL write Not very sure about this one. The spec 18.2.4.2 mentions "IA32_PERF_GLOBAL_STATUS_RESET provides additional bit fields to clear the new indicators.." IIUIC, the new freeze bits can only be cleared by RESET. But the guest KVM pmu doesn't support v4 so far, so the only way to clear it is through DEBUGCTL. STATUS_RESET would only be needed to set it from the guest, which is not necessary at least for now (and would be also v4) At some point the guest PMU should probably be updated for v4, but it can be done separately from this. Agree. I think the guest perf won't work in v4 mode if the KVM vPMU exposes it is v3. Probably we could also leave the freeze bits virtualization support to another series of vPMU v4 support? We would also need to use the STATUS_SET in v4 to set the freeze bits of GLOBAL_STATUS when entering the guest (instead of clearing the guest debugctl), so that we could achieve architectural emulation. Best, Wei
Re: [PATCH v5 12/12] KVM/VMX/vPMU: support to report GLOBAL_STATUS_LBRS_FROZEN
On Fri, Feb 15, 2019 at 08:56:02AM +, Wang, Wei W wrote:
> On Friday, February 15, 2019 12:32 AM, Andi Kleen wrote:
> >
> > > +static void intel_pmu_get_global_status(struct kvm_pmu *pmu,
> > > + struct msr_data *msr_info)
> > > +{
> > > + u64 guest_debugctl, freeze_lbr_bits =
> > DEBUGCTLMSR_FREEZE_LBRS_ON_PMI |
> > > + DEBUGCTLMSR_LBR;
> > > +
> > > + if (!pmu->global_status) {
> > > + msr_info->data = 0;
> > > + return;
> > > + }
> > > +
> > > + msr_info->data = pmu->global_status;
> > > + if (pmu->version >= 4) {
> > > + guest_debugctl = vmcs_read64(GUEST_IA32_DEBUGCTL);
> > > + if ((guest_debugctl & freeze_lbr_bits) == freeze_lbr_bits)
> >
> > It should only check for the freeze bit, the freeze bit can be set even when
> > LBRs are disabled.
> >
> > Also you seem to set the bit unconditionally?
> > That doesn't seem right. It should only be set after an overflow.
> >
> > So the PMI injection needs to set it.
>
> OK. The freeze bits need to be cleared by IA32_PERF_GLOBAL_STATUS_RESET,
> which seems not supported by the perf code yet (thus guest won't clear them).
> Would handle_irq_v4 also need to be changed to support that?
In Arch Perfmon v4 it is cleared by the MSR_CORE_PERF_GLOBAL_OVF_CTRL write
But the guest KVM pmu doesn't support v4 so far, so the only way to clear it is
through DEBUGCTL.
STATUS_RESET would only be needed to set it from the guest, which is not
necessary at least for now
(and would be also v4)
At some point the guest PMU should probably be updated for v4, but it can be
done
separately from this.
-Andi
RE: [PATCH v5 12/12] KVM/VMX/vPMU: support to report GLOBAL_STATUS_LBRS_FROZEN
On Friday, February 15, 2019 12:32 AM, Andi Kleen wrote:
>
> > +static void intel_pmu_get_global_status(struct kvm_pmu *pmu,
> > + struct msr_data *msr_info)
> > +{
> > + u64 guest_debugctl, freeze_lbr_bits =
> DEBUGCTLMSR_FREEZE_LBRS_ON_PMI |
> > + DEBUGCTLMSR_LBR;
> > +
> > + if (!pmu->global_status) {
> > + msr_info->data = 0;
> > + return;
> > + }
> > +
> > + msr_info->data = pmu->global_status;
> > + if (pmu->version >= 4) {
> > + guest_debugctl = vmcs_read64(GUEST_IA32_DEBUGCTL);
> > + if ((guest_debugctl & freeze_lbr_bits) == freeze_lbr_bits)
>
> It should only check for the freeze bit, the freeze bit can be set even when
> LBRs are disabled.
>
> Also you seem to set the bit unconditionally?
> That doesn't seem right. It should only be set after an overflow.
>
> So the PMI injection needs to set it.
OK. The freeze bits need to be cleared by IA32_PERF_GLOBAL_STATUS_RESET, which
seems not supported by the perf code yet (thus guest won't clear them). Would
handle_irq_v4 also need to be changed to support that?
Best,
Wei
Re: [PATCH v5 12/12] KVM/VMX/vPMU: support to report GLOBAL_STATUS_LBRS_FROZEN
> +static void intel_pmu_get_global_status(struct kvm_pmu *pmu,
> + struct msr_data *msr_info)
> +{
> + u64 guest_debugctl, freeze_lbr_bits = DEBUGCTLMSR_FREEZE_LBRS_ON_PMI |
> + DEBUGCTLMSR_LBR;
> +
> + if (!pmu->global_status) {
> + msr_info->data = 0;
> + return;
> + }
> +
> + msr_info->data = pmu->global_status;
> + if (pmu->version >= 4) {
> + guest_debugctl = vmcs_read64(GUEST_IA32_DEBUGCTL);
> + if ((guest_debugctl & freeze_lbr_bits) == freeze_lbr_bits)
It should only check for the freeze bit, the freeze bit can be set
even when LBRs are disabled.
Also you seem to set the bit unconditionally?
That doesn't seem right. It should only be set after an overflow.
So the PMI injection needs to set it.
-Andi
