public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Liang, Kan" <kan.liang@linux.intel.com>
To: "Yang, Weijiang" <weijiang.yang@intel.com>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	"jmattson@google.com" <jmattson@google.com>,
	"seanjc@google.com" <seanjc@google.com>,
	"like.xu.linux@gmail.com" <like.xu.linux@gmail.com>,
	"vkuznets@redhat.com" <vkuznets@redhat.com>,
	"Wang, Wei W" <wei.w.wang@intel.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v11 08/16] KVM: x86/pmu: Refactor code to support guest Arch LBR
Date: Mon, 9 May 2022 10:06:07 -0400	[thread overview]
Message-ID: <59e62b5b-beed-daef-971b-864a41928446@linux.intel.com> (raw)
In-Reply-To: <d2e14530-f3c1-53c9-dd03-95ea2c1bf3f1@intel.com>



On 5/6/2022 10:32 PM, Yang, Weijiang wrote:
> 
> On 5/6/2022 11:03 PM, Liang, Kan wrote:
>> On 5/5/2022 11:32 PM, Yang Weijiang wrote:
>>
>>    bool intel_pmu_lbr_is_enabled(struct kvm_vcpu *vcpu)
>> @@ -199,12 +203,20 @@ static bool intel_pmu_is_valid_lbr_msr(struct 
>> kvm_vcpu *vcpu, u32 index)
>>            return ret;
>>        }
>> -    ret = (index == MSR_LBR_SELECT) || (index == MSR_LBR_TOS) ||
>> -        (index >= records->from && index < records->from + 
>> records->nr) ||
>> -        (index >= records->to && index < records->to + records->nr);
>> +    if (!guest_cpuid_has(vcpu, X86_FEATURE_ARCH_LBR))
>> +        ret = (index == MSR_LBR_SELECT) || (index == MSR_LBR_TOS);
>> +
>> Shouldn't we return immediately if (ret == true)?
>> Keep checking if (!ret) looks uncommon.
>>
>> Actually we probably don't need the ret in this function.
>>
>>     if (!guest_cpuid_has(vcpu, X86_FEATURE_ARCH_LBR) &&
>>         ((index == MSR_LBR_SELECT) || (index == MSR_LBR_TOS)))
>>         return true;
>>
>>> +    if (!ret) {
>>> +        ret = (index >= records->from &&
>>> +               index < records->from + records->nr) ||
>>> +              (index >= records->to &&
>>> +               index < records->to + records->nr);
>>> +    }
>>     if ((index >= records->from &&
>>         index < records->from + records->nr) ||
>>         (index >= records->to &&
>>         index < records->to + records->nr))
>>         return true;
>>
>>> -    if (!ret && records->info)
>>> -        ret = (index >= records->info && index < records->info + 
>>> records->nr);
>>> +    if (!ret && records->info) {
>>> +        ret = (index >= records->info &&
>>> +               index < records->info + records->nr);
>>> +    }
>>     if (records->info &&
>>         (index >= records->info && index < records->info + records->nr)
>>         return true;
>>
>>     return false;
>> Sorry, I didn't notice it in the previous review.
> 
> Thanks Kan, so I'll modify this function as below (keeping other part 
> unchanged):
> 
>  From 642d5e05e8a8578e75531632d714cec5976ab9ac Mon Sep 17 00:00:00 2001
> From: Yang Weijiang <weijiang.yang@intel.com>
> Date: Thu, 8 Jul 2021 23:51:02 +0800
> Subject: [PATCH] KVM: x86/pmu: Refactor code to support guest Arch LBR
> 
> Take account of Arch LBR when do sanity checks before program
> vPMU for guest. Pass through Arch LBR recording MSRs to guest
> to gain better performance. Note, Arch LBR and Legacy LBR support
> are mutually exclusive, i.e., they're not both available on one
> platform.
> 
> Co-developed-by: Like Xu <like.xu@linux.intel.com>
> Signed-off-by: Like Xu <like.xu@linux.intel.com>
> Signed-off-by: Yang Weijiang <weijiang.yang@intel.com>
> ---

This one looks good to me.

Reviewed-by: Kan Liang <kan.liang@linux.intel.com>

Thanks,
Kan
>   arch/x86/kvm/vmx/pmu_intel.c | 47 +++++++++++++++++++++++++-----------
>   arch/x86/kvm/vmx/vmx.c       |  3 +++
>   2 files changed, 36 insertions(+), 14 deletions(-)
> 
> diff --git a/arch/x86/kvm/vmx/pmu_intel.c b/arch/x86/kvm/vmx/pmu_intel.c
> index aa36d2072b91..306ce7ac9934 100644
> --- a/arch/x86/kvm/vmx/pmu_intel.c
> +++ b/arch/x86/kvm/vmx/pmu_intel.c
> @@ -170,12 +170,16 @@ static inline struct kvm_pmc *get_fw_gp_pmc(struct 
> kvm_pmu *pmu, u32 msr)
> 
>   bool intel_pmu_lbr_is_compatible(struct kvm_vcpu *vcpu)
>   {
> +       if (kvm_cpu_cap_has(X86_FEATURE_ARCH_LBR))
> +               return guest_cpuid_has(vcpu, X86_FEATURE_ARCH_LBR);
> +
>          /*
>           * As a first step, a guest could only enable LBR feature if its
>           * cpu model is the same as the host because the LBR registers
>           * would be pass-through to the guest and they're model specific.
>           */
> -       return boot_cpu_data.x86_model == guest_cpuid_model(vcpu);
> +       return !boot_cpu_has(X86_FEATURE_ARCH_LBR) &&
> +               boot_cpu_data.x86_model == guest_cpuid_model(vcpu);
>   }
> 
>   bool intel_pmu_lbr_is_enabled(struct kvm_vcpu *vcpu)
> @@ -188,25 +192,28 @@ bool intel_pmu_lbr_is_enabled(struct kvm_vcpu *vcpu)
>   static bool intel_pmu_is_valid_lbr_msr(struct kvm_vcpu *vcpu, u32 index)
>   {
>          struct x86_pmu_lbr *records = vcpu_to_lbr_records(vcpu);
> -       bool ret = false;
> 
>          if (!intel_pmu_lbr_is_enabled(vcpu))
> -               return ret;
> +               return false;
> 
>          if (index == MSR_ARCH_LBR_DEPTH || index == MSR_ARCH_LBR_CTL) {
> -               if (kvm_cpu_cap_has(X86_FEATURE_ARCH_LBR))
> -                       ret = guest_cpuid_has(vcpu, X86_FEATURE_ARCH_LBR);
> -               return ret;
> +               return kvm_cpu_cap_has(X86_FEATURE_ARCH_LBR) &&
> +                      guest_cpuid_has(vcpu, X86_FEATURE_ARCH_LBR);
>          }
> 
> -       ret = (index == MSR_LBR_SELECT) || (index == MSR_LBR_TOS) ||
> -               (index >= records->from && index < records->from + 
> records->nr) ||
> -               (index >= records->to && index < records->to + 
> records->nr);
> +       if (!guest_cpuid_has(vcpu, X86_FEATURE_ARCH_LBR) &&
> +           (index == MSR_LBR_SELECT || index == MSR_LBR_TOS))
> +               return true;
> 
> -       if (!ret && records->info)
> -               ret = (index >= records->info && index < records->info + 
> records->nr);
> +       if ((index >= records->from && index < records->from + 
> records->nr) ||
> +           (index >= records->to && index < records->to + records->nr))
> +               return true;
> 
> -       return ret;
> +       if (records->info && index >= records->info &&
> +           index < records->info + records->nr)
> +               return true;
> +
> +       return false;
>   }
> 
>   static bool intel_is_valid_msr(struct kvm_vcpu *vcpu, u32 msr)
> @@ -742,6 +749,9 @@ static void vmx_update_intercept_for_lbr_msrs(struct 
> kvm_vcpu *vcpu, bool set)
>                          vmx_set_intercept_for_msr(vcpu, lbr->info + i, 
> MSR_TYPE_RW, set);
>          }
> 
> +       if (guest_cpuid_has(vcpu, X86_FEATURE_ARCH_LBR))
> +               return;
> +
>          vmx_set_intercept_for_msr(vcpu, MSR_LBR_SELECT, MSR_TYPE_RW, set);
>          vmx_set_intercept_for_msr(vcpu, MSR_LBR_TOS, MSR_TYPE_RW, set);
>   }
> @@ -782,10 +792,13 @@ void vmx_passthrough_lbr_msrs(struct kvm_vcpu *vcpu)
>   {
>          struct kvm_pmu *pmu = vcpu_to_pmu(vcpu);
>          struct lbr_desc *lbr_desc = vcpu_to_lbr_desc(vcpu);
> +       bool lbr_enable = guest_cpuid_has(vcpu, X86_FEATURE_ARCH_LBR) ?
> +               (vmcs_read64(GUEST_IA32_LBR_CTL) & ARCH_LBR_CTL_LBREN) :
> +               (vmcs_read64(GUEST_IA32_DEBUGCTL) & DEBUGCTLMSR_LBR);
> 
>          if (!lbr_desc->event) {
>                  vmx_disable_lbr_msrs_passthrough(vcpu);
> -               if (vmcs_read64(GUEST_IA32_DEBUGCTL) & DEBUGCTLMSR_LBR)
> +               if (lbr_enable)
>                          goto warn;
>                  if (test_bit(INTEL_PMC_IDX_FIXED_VLBR, pmu->pmc_in_use))
>                          goto warn;
> @@ -802,13 +815,19 @@ void vmx_passthrough_lbr_msrs(struct kvm_vcpu *vcpu)
>          return;
> 
>   warn:
> +       if (kvm_cpu_cap_has(X86_FEATURE_ARCH_LBR))
> +               wrmsrl(MSR_ARCH_LBR_DEPTH, lbr_desc->records.nr);
>          pr_warn_ratelimited("kvm: vcpu-%d: fail to passthrough LBR.\n",
>                  vcpu->vcpu_id);
>   }
> 
>   static void intel_pmu_cleanup(struct kvm_vcpu *vcpu)
>   {
> -       if (!(vmcs_read64(GUEST_IA32_DEBUGCTL) & DEBUGCTLMSR_LBR))
> +       bool lbr_enable = guest_cpuid_has(vcpu, X86_FEATURE_ARCH_LBR) ?
> +               (vmcs_read64(GUEST_IA32_LBR_CTL) & ARCH_LBR_CTL_LBREN) :
> +               (vmcs_read64(GUEST_IA32_DEBUGCTL) & DEBUGCTLMSR_LBR);
> +
> +       if (!lbr_enable)
>                  intel_pmu_release_guest_lbr_event(vcpu);
>   }
> 
> diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
> index b6bc7d97e4b4..98e56a909c01 100644
> --- a/arch/x86/kvm/vmx/vmx.c
> +++ b/arch/x86/kvm/vmx/vmx.c
> @@ -573,6 +573,9 @@ static bool is_valid_passthrough_msr(u32 msr)
>          case MSR_LBR_NHM_TO ... MSR_LBR_NHM_TO + 31:
>          case MSR_LBR_CORE_FROM ... MSR_LBR_CORE_FROM + 8:
>          case MSR_LBR_CORE_TO ... MSR_LBR_CORE_TO + 8:
> +       case MSR_ARCH_LBR_FROM_0 ... MSR_ARCH_LBR_FROM_0 + 31:
> +       case MSR_ARCH_LBR_TO_0 ... MSR_ARCH_LBR_TO_0 + 31:
> +       case MSR_ARCH_LBR_INFO_0 ... MSR_ARCH_LBR_INFO_0 + 31:
>                  /* LBR MSRs. These are handled in 
> vmx_update_intercept_for_lbr_msrs() */
>                  return true;
>          }
> -- 
> 2.27.0
> 
>> Thanks,
>> Kan
>>

  reply	other threads:[~2022-05-09 14:06 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06  3:32 [PATCH v11 00/16] Introduce Architectural LBR for vPMU Yang Weijiang
2022-05-06  3:32 ` [PATCH v11 01/16] perf/x86/intel: Fix the comment about guest LBR support on KVM Yang Weijiang
2022-05-06  3:32 ` [PATCH v11 02/16] perf/x86/lbr: Simplify the exposure check for the LBR_INFO registers Yang Weijiang
2022-05-06  3:32 ` [PATCH v11 03/16] KVM: x86: Report XSS as an MSR to be saved if there are supported features Yang Weijiang
2022-05-06  3:32 ` [PATCH v11 04/16] KVM: x86: Refresh CPUID on writes to MSR_IA32_XSS Yang Weijiang
2022-05-06  3:32 ` [PATCH v11 05/16] KVM: x86: Add Arch LBR MSRs to msrs_to_save_all list Yang Weijiang
2022-05-06  3:32 ` [PATCH v11 06/16] KVM: vmx/pmu: Emulate MSR_ARCH_LBR_DEPTH for guest Arch LBR Yang Weijiang
2022-05-06 14:39   ` Liang, Kan
2022-05-06  3:32 ` [PATCH v11 07/16] KVM: vmx/pmu: Emulate MSR_ARCH_LBR_CTL " Yang Weijiang
2022-05-06 14:42   ` Liang, Kan
2022-05-06  3:32 ` [PATCH v11 08/16] KVM: x86/pmu: Refactor code to support " Yang Weijiang
2022-05-06 15:03   ` Liang, Kan
2022-05-07  2:32     ` Yang, Weijiang
2022-05-09 14:06       ` Liang, Kan [this message]
2022-05-06  3:32 ` [PATCH v11 09/16] KVM: x86: Refine the matching and clearing logic for supported_xss Yang Weijiang
2022-05-06  3:32 ` [PATCH v11 10/16] KVM: x86: Add XSAVE Support for Architectural LBR Yang Weijiang
2022-05-06  3:33 ` [PATCH v11 11/16] KVM: x86/vmx: Check Arch LBR config when return perf capabilities Yang Weijiang
2022-05-06  3:33 ` [PATCH v11 12/16] KVM: nVMX: Add necessary Arch LBR settings for nested VM Yang Weijiang
2022-05-06  3:33 ` [PATCH v11 13/16] KVM: x86/vmx: Clear Arch LBREn bit before inject #DB to guest Yang Weijiang
2022-05-06 15:08   ` Liang, Kan
2022-05-06  3:33 ` [PATCH v11 14/16] KVM: x86/vmx: Flip Arch LBREn bit on guest state change Yang Weijiang
2022-05-06 15:08   ` Liang, Kan
2022-05-10 15:51   ` Paolo Bonzini
2022-05-11  7:43     ` Yang, Weijiang
2022-05-12 13:18       ` Paolo Bonzini
2022-05-12 14:38         ` Yang, Weijiang
2022-05-13  4:02         ` Yang, Weijiang
2022-05-17  8:56           ` Yang, Weijiang
2022-05-17  9:01             ` Paolo Bonzini
2022-05-17 11:31               ` Yang, Weijiang
2022-05-12  6:44     ` Yang, Weijiang
2022-05-06  3:33 ` [PATCH v11 15/16] KVM: x86: Add Arch LBR data MSR access interface Yang Weijiang
2022-05-06 15:11   ` Liang, Kan
2022-05-06  3:33 ` [PATCH v11 16/16] KVM: x86/cpuid: Advertise Arch LBR feature in CPUID Yang Weijiang
2022-05-06 15:13   ` Liang, Kan
2022-05-10 15:55 ` [PATCH v11 00/16] Introduce Architectural LBR for vPMU Paolo Bonzini
2022-05-11  0:29   ` Yang, Weijiang

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=59e62b5b-beed-daef-971b-864a41928446@linux.intel.com \
    --to=kan.liang@linux.intel.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=like.xu.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=vkuznets@redhat.com \
    --cc=wei.w.wang@intel.com \
    --cc=weijiang.yang@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