From: Paolo Bonzini <pbonzini@redhat.com>
To: Phil Dennis-Jordan <phil@philjordan.eu>, qemu-devel@nongnu.org
Cc: Richard Henderson <rth@twiddle.net>,
Eduardo Habkost <ehabkost@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH] x86-KVM: Supply TSC and APIC clock rates to guest like VMWare
Date: Wed, 18 Jan 2017 16:05:59 +0100 [thread overview]
Message-ID: <aae83060-472d-97fb-9ada-2a78ff3f815f@redhat.com> (raw)
In-Reply-To: <1484749457-87117-1-git-send-email-phil@philjordan.eu>
On 18/01/2017 15:24, Phil Dennis-Jordan wrote:
> ---
> target/i386/cpu.c | 1 +
> target/i386/cpu.h | 4 ++++
> target/i386/kvm.c | 40 ++++++++++++++++++++++++++++++++--------
> 3 files changed, 37 insertions(+), 8 deletions(-)
>
> diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> index aba11ae..e5523d4 100644
> --- a/target/i386/cpu.c
> +++ b/target/i386/cpu.c
> @@ -3677,6 +3677,7 @@ static Property x86_cpu_properties[] = {
> DEFINE_PROP_BOOL("cpuid-0xb", X86CPU, enable_cpuid_0xb, true),
> DEFINE_PROP_BOOL("lmce", X86CPU, enable_lmce, false),
> DEFINE_PROP_BOOL("l3-cache", X86CPU, enable_l3_cache, true),
> + DEFINE_PROP_BOOL("vmware-tsc-apic-clocks", X86CPU, vmware_clock_rates, false),
Maybe just vmware-cpuid-freq instead? Whatever the choice, please make
the bool field in struct X86CPU consistent with the property name (e.g.
enable_vmware_cpuid_freq).
One issue is that the TSC frequency can change, for example on
migration. Telling the guest about the TSC frequency makes little sense
if it can change.
So the leaf should be conditional on the INVTSC feature
(CPUID[0x80000007].EDX bit 8). You can enable this unconditionally for
new machine types (i.e. making it true here, and turning it off in
include/hw/i386/pc.h's PC_COMPAT_2_8 macro), but only expose it if that
bit is also set.
> DEFINE_PROP_END_OF_LIST()
> };
>
> diff --git a/target/i386/cpu.h b/target/i386/cpu.h
> index 6c1902b..1d8590b 100644
> --- a/target/i386/cpu.h
> +++ b/target/i386/cpu.h
> @@ -1213,6 +1213,10 @@ struct X86CPU {
> bool host_features;
> uint32_t apic_id;
>
> + /* Enables publishing of TSC increment and Local APIC bus frequencies to
> + * the guest OS in CPUID page 0x40000010, the same way that VMWare does. */
> + bool vmware_clock_rates;
> +
> /* if true the CPUID code directly forward host cache leaves to the guest */
> bool cache_info_passthrough;
>
> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> index 10a9cd8..7830b3a 100644
> --- a/target/i386/kvm.c
> +++ b/target/i386/kvm.c
> @@ -778,10 +778,14 @@ int kvm_arch_init_vcpu(CPUState *cs)
> }
>
> if (cpu->expose_kvm) {
> + uint32_t kvm_max_page = KVM_CPUID_FEATURES | kvm_base;
s/page/leaf/
> + if (cpu->vmware_clock_rates && kvm_base == KVM_CPUID_SIGNATURE) {
> + kvm_max_page = MAX(kvm_max_page, KVM_CPUID_SIGNATURE | 0x10);
> + }
> memcpy(signature, "KVMKVMKVM\0\0\0", 12);
> c = &cpuid_data.entries[cpuid_i++];
> c->function = KVM_CPUID_SIGNATURE | kvm_base;
> - c->eax = KVM_CPUID_FEATURES | kvm_base;
> + c->eax = kvm_max_page;
> c->ebx = signature[0];
> c->ecx = signature[1];
> c->edx = signature[2];
> @@ -910,7 +914,6 @@ int kvm_arch_init_vcpu(CPUState *cs)
> }
> }
>
> - cpuid_data.cpuid.nent = cpuid_i;
>
> if (((env->cpuid_version >> 8)&0xF) >= 6
> && (env->features[FEAT_1_EDX] & (CPUID_MCE | CPUID_MCA)) ==
> @@ -973,12 +976,6 @@ int kvm_arch_init_vcpu(CPUState *cs)
> vmstate_x86_cpu.unmigratable = 1;
> }
>
> - cpuid_data.cpuid.padding = 0;
> - r = kvm_vcpu_ioctl(cs, KVM_SET_CPUID2, &cpuid_data);
> - if (r) {
> - return r;
> - }
> -
> r = kvm_arch_set_tsc_khz(cs);
> if (r < 0) {
> return r;
> @@ -998,6 +995,33 @@ int kvm_arch_init_vcpu(CPUState *cs)
> }
> }
>
> + if (cpu->vmware_clock_rates) {
^^ Here is where you should also check invtsc.
> + if (cpu->expose_kvm
I think this should not depend on cpu->expose_kvm. This is not a KVM
leaf, it's a vmware leaf; if it were a KVM leaf, it would obey kvm_base.
Of course checking kvm_base is still a good idea, to avoid stomping on
Hyper-V's CPUID space.
Thanks,
Paolo
> + && kvm_base == KVM_CPUID_SIGNATURE
> + && env->tsc_khz != 0) {
> + /* Publish TSC and LAPIC resolution on CPUID page 0x40000010
> + * like VMWare for benefit of Darwin guests. */
> + c = &cpuid_data.entries[cpuid_i++];
> + c->function = KVM_CPUID_SIGNATURE | 0x10;
> + c->eax = env->tsc_khz;
> + /* LAPIC resolution of 1ns (freq: 1GHz) is hardcoded in KVM's
> + * APIC_BUS_CYCLE_NS*/
> + c->ebx = 1000000;
> + c->ecx = c->edx = 0;
> + } else {
> + error_report(
> + "Warning: VMWare-style TSC/LAPIC clock reporting impossible.");
> + }
> + }
> +
> + cpuid_data.cpuid.nent = cpuid_i;
> +
> + cpuid_data.cpuid.padding = 0;
> + r = kvm_vcpu_ioctl(cs, KVM_SET_CPUID2, &cpuid_data);
> + if (r) {
> + return r;
> + }
> +
> if (has_xsave) {
> env->kvm_xsave_buf = qemu_memalign(4096, sizeof(struct kvm_xsave));
> }
>
next prev parent reply other threads:[~2017-01-18 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 14:24 [Qemu-devel] [PATCH] x86-KVM: Supply TSC and APIC clock rates to guest like VMWare Phil Dennis-Jordan
2017-01-18 15:05 ` Paolo Bonzini [this message]
2017-01-18 15:23 ` Eduardo Habkost
2017-01-18 16:02 ` Phil Dennis-Jordan
2017-01-18 16:10 ` Paolo Bonzini
2017-01-18 16:16 ` Phil Dennis-Jordan
2017-01-18 16:22 ` Paolo Bonzini
2017-01-18 16:04 ` Phil Dennis-Jordan
2017-01-18 17:15 ` Eduardo Habkost
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=aae83060-472d-97fb-9ada-2a78ff3f815f@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=phil@philjordan.eu \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).