From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Like Xu <like.xu@linux.intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
wei.huang2@amd.com, Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Li RongQing <lirongqing@baidu.com>,
Chai Wen <chaiwen@baidu.com>, Jia Lina <jialina01@baidu.com>
Subject: Re: [PATCH] KVM: X86: Emulate APERF/MPERF to report actual VCPU frequency
Date: Tue, 23 Jun 2020 11:29:10 -0700 [thread overview]
Message-ID: <20200623182910.GA24107@linux.intel.com> (raw)
In-Reply-To: <20200623063530.81917-1-like.xu@linux.intel.com>
On Tue, Jun 23, 2020 at 02:35:30PM +0800, Like Xu wrote:
> The aperf/mperf are used to report current CPU frequency after 7d5905dc14a
> "x86 / CPU: Always show current CPU frequency in /proc/cpuinfo". But guest
> kernel always reports a fixed VCPU frequency in the /proc/cpuinfo, which
> may confuse users especially when turbo is enabled on the host.
>
> Emulate guest APERF/MPERF capability based their values on the host.
>
> Co-developed-by: Li RongQing <lirongqing@baidu.com>
> Signed-off-by: Li RongQing <lirongqing@baidu.com>
> Reviewed-by: Chai Wen <chaiwen@baidu.com>
> Reviewed-by: Jia Lina <jialina01@baidu.com>
> Signed-off-by: Like Xu <like.xu@linux.intel.com>
> ---
...
> @@ -8312,7 +8376,7 @@ static int vcpu_enter_guest(struct kvm_vcpu *vcpu)
> dm_request_for_irq_injection(vcpu) &&
> kvm_cpu_accept_dm_intr(vcpu);
> fastpath_t exit_fastpath;
> -
> + u64 enter_mperf = 0, enter_aperf = 0, exit_mperf = 0, exit_aperf = 0;
> bool req_immediate_exit = false;
>
> if (kvm_request_pending(vcpu)) {
> @@ -8516,8 +8580,17 @@ static int vcpu_enter_guest(struct kvm_vcpu *vcpu)
> vcpu->arch.switch_db_regs &= ~KVM_DEBUGREG_RELOAD;
> }
>
> + if (unlikely(vcpu->arch.hwp.hw_coord_fb_cap))
> + get_host_amperf(&enter_mperf, &enter_aperf);
> +
> exit_fastpath = kvm_x86_ops.run(vcpu);
>
> + if (unlikely(vcpu->arch.hwp.hw_coord_fb_cap)) {
> + get_host_amperf(&exit_mperf, &exit_aperf);
> + vcpu_update_amperf(vcpu, get_amperf_delta(enter_aperf, exit_aperf),
> + get_amperf_delta(enter_mperf, exit_mperf));
> + }
> +
Is there an alternative approach that doesn't require 4 RDMSRs on every VMX
round trip? That's literally more expensive than VM-Enter + VM-Exit
combined.
E.g. what about adding KVM_X86_DISABLE_EXITS_APERF_MPERF and exposing the
MSRs for read when that capability is enabled?
next prev parent reply other threads:[~2020-06-23 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 6:35 [PATCH] KVM: X86: Emulate APERF/MPERF to report actual VCPU frequency Like Xu
2020-06-23 18:29 ` Sean Christopherson [this message]
2020-06-23 18:39 ` Jim Mattson
2020-06-23 19:05 ` Sean Christopherson
2020-06-23 20:34 ` Jim Mattson
2021-12-22 6:56 ` Like Xu
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=20200623182910.GA24107@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=chaiwen@baidu.com \
--cc=jialina01@baidu.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=like.xu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=wei.huang2@amd.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;
as well as URLs for NNTP newsgroup(s).