From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [PATCH v4 01/16] xen: Add support for VMware cpuid leaves Date: Thu, 11 Sep 2014 20:49:33 +0100 Message-ID: <5411FCCD.2000707@citrix.com> References: <1410460610-14759-1-git-send-email-dslutz@verizon.com> <1410460610-14759-2-git-send-email-dslutz@verizon.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1410460610-14759-2-git-send-email-dslutz@verizon.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Don Slutz , xen-devel@lists.xen.org Cc: Kevin Tian , Keir Fraser , Ian Campbell , Stefano Stabellini , Jun Nakajima , Eddie Dong , Ian Jackson , Tim Deegan , George Dunlap , Aravind Gopalakrishnan , Jan Beulich , Boris Ostrovsky , Suravee Suthikulpanit List-Id: xen-devel@lists.xenproject.org On 11/09/2014 19:36, Don Slutz wrote: > This is done by adding HVM_PARAM_VMWARE_HW. It is set to the VMware > virtual hardware version. > > Currently 0, 3-4, 6-11 are good values. However the > code only checks for == 0 or != 0. > > If non-zero then > Return VMware's cpuid leaves. > > The support of hypervisor cpuid leaves has not been agreed to. > > MicroSoft Hyper-V (AKA viridian) currently must be at 0x40000000. > > VMware currently must be at 0x40000000. > > KVM currently must be at 0x40000000 (from Seabios). > > Seabios will find xen at 0x40000000, 0x40000100, 0x40000200 .. > 0x40010000. > > http://download.microsoft.com/download/F/B/0/FB0D01A3-8E3A-4F5F-AA59-08C8026D3B8A/requirements-for-implementing-microsoft-hypervisor-interface.docx > > http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1009458 > > http://lwn.net/Articles/301888/ > Attempted to get this cleaned up. > > So based on this, I picked the order: > > Xen at 0x40000000 or > Viridian or VMware at 0x40000000 and Xen at 0x40000100 > > If both Viridian and VMware selected, report an error. > > Signed-off-by: Don Slutz > --- > xen/arch/x86/hvm/Makefile | 3 +- > xen/arch/x86/hvm/hvm.c | 32 +++++++++++++++++++ > xen/arch/x86/hvm/vmware/Makefile | 1 + > xen/arch/x86/hvm/vmware/cpuid.c | 69 ++++++++++++++++++++++++++++++++++++++++ > xen/arch/x86/traps.c | 8 +++-- > xen/include/asm-x86/hvm/hvm.h | 3 ++ > xen/include/asm-x86/hvm/vmware.h | 31 ++++++++++++++++++ > xen/include/public/hvm/params.h | 5 ++- > 8 files changed, 148 insertions(+), 4 deletions(-) > create mode 100644 xen/arch/x86/hvm/vmware/Makefile > create mode 100644 xen/arch/x86/hvm/vmware/cpuid.c > create mode 100644 xen/include/asm-x86/hvm/vmware.h > > diff --git a/xen/arch/x86/hvm/Makefile b/xen/arch/x86/hvm/Makefile > index eea5555..77598a6 100644 > --- a/xen/arch/x86/hvm/Makefile > +++ b/xen/arch/x86/hvm/Makefile > @@ -1,5 +1,6 @@ > subdir-y += svm > subdir-y += vmx > +subdir-y += vmware > > obj-y += asid.o > obj-y += emulate.o > @@ -22,4 +23,4 @@ obj-y += vlapic.o > obj-y += vmsi.o > obj-y += vpic.o > obj-y += vpt.o > -obj-y += vpmu.o > \ No newline at end of file > +obj-y += vpmu.o This hunk is unrelated, but is perhaps something better fixed. A passing note in the commit message perhaps? > diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c > index 8d905d3..03a1a19 100644 > --- a/xen/arch/x86/hvm/hvm.c > +++ b/xen/arch/x86/hvm/hvm.c > @@ -57,6 +57,7 @@ > #include > #include > #include > +#include > #include > #include > #include > @@ -4228,6 +4229,9 @@ void hvm_cpuid(unsigned int input, unsigned int *eax, unsigned int *ebx, > if ( cpuid_viridian_leaves(input, eax, ebx, ecx, edx) ) > return; > > + if ( cpuid_vmware_leaves(input, eax, ebx, ecx, edx) ) > + return; > + > if ( cpuid_hypervisor_leaves(input, count, eax, ebx, ecx, edx) ) > return; > > @@ -5555,6 +5559,11 @@ long do_hvm_op(unsigned long op, XEN_GUEST_HANDLE_PARAM(void) arg) > rc = -EINVAL; > break; > case HVM_PARAM_VIRIDIAN: > + if ( d->arch.hvm_domain.params[HVM_PARAM_VMWARE_HW] ) > + { > + rc = -EXDEV; > + break; > + } > if ( a.value > 1 ) > rc = -EINVAL; > break; > @@ -5692,6 +5701,29 @@ long do_hvm_op(unsigned long op, XEN_GUEST_HANDLE_PARAM(void) arg) > > break; > } > + case HVM_PARAM_VMWARE_HW: > + /* > + * This should only ever be set non-zero one time by > + * the tools and is read only by the guest. > + */ > + if ( d == current->domain ) > + { > + rc = -EPERM; > + break; > + } > + if ( d->arch.hvm_domain.params[HVM_PARAM_VIRIDIAN] ) > + { > + rc = -EXDEV; > + break; > + } > + if ( d->arch.hvm_domain.params[HVM_PARAM_VMWARE_HW] && > + d->arch.hvm_domain.params[HVM_PARAM_VMWARE_HW] != > + a.value ) > + { > + rc = -EEXIST; > + break; > + } > + break; Eugh - its code like this which is why I am certain that things such as VIRIDIAN, VMWARE (and NESTED_VIRT for that matter) should be domain creation flags rather than hvm params, and completely immutable for the entire lifetime of the domain. After all, these params are only being used as glorified, set-once booleans. I even have an in-progress patch to turn VIRIDIAN into a create flag (which has now been complicated by VIRIDIAN turning into a bitmask), but it appear that doing this necessitates breaking the Libxl API. For reasons which elude me, the Libxl API exposes the internal implementation details between "domain creation information" and "domain build information" in such a way that I couldn't find a compatible way of moving information from from the latter to the former. (i.e. you can't duplicate the same field in the create info and still have a user of an old libxl API version still have their domain creation work when they only specify the value in the build info) I am not sure how "fixing things correctly in Xen" fairs against "libxl taking pain and possibly an API breakage because it previously exposed internal details which it shouldn't have done", but I would prefer that we didn't make the problem any harder to fix than it already is. As a result, I am formally suggesting that this would be better done by adding a domain creation flag (although not being a maintainer, I realise my views in this matter don't strictly count for much). > } > > if ( rc == 0 ) > diff --git a/xen/arch/x86/hvm/vmware/Makefile b/xen/arch/x86/hvm/vmware/Makefile > new file mode 100644 > index 0000000..3fb2e0b > --- /dev/null > +++ b/xen/arch/x86/hvm/vmware/Makefile > @@ -0,0 +1 @@ > +obj-y += cpuid.o > diff --git a/xen/arch/x86/hvm/vmware/cpuid.c b/xen/arch/x86/hvm/vmware/cpuid.c > new file mode 100644 > index 0000000..730ab8f > --- /dev/null > +++ b/xen/arch/x86/hvm/vmware/cpuid.c > @@ -0,0 +1,69 @@ > +/* > + * arch/x86/hvm/vmware/cpuid.c > + * > + * Copyright (C) 2012 Verizon Corporation > + * > + * This file is free software; you can redistribute it and/or modify it > + * under the terms of the GNU General Public License Version 2 (GPLv2) > + * as published by the Free Software Foundation. > + * > + * This file is distributed in the hope that it will be useful, > + * but WITHOUT ANY WARRANTY; without even the implied warranty of > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU > + * General Public License for more details. . > + */ > + > +#include > + > +#include > +#include > + > +int cpuid_vmware_leaves(uint32_t idx, uint32_t *eax, uint32_t *ebx, > + uint32_t *ecx, uint32_t *edx) > +{ > + struct domain *d = current->domain; > + > + if ( !is_vmware_domain(d) ) > + return 0; > + > + switch ( idx - 0x40000000 ) > + { > + case 0x0: Do these leaves have semantic names from a spec, which could live in an appropriate header file? > + *eax = 0x40000010; /* Largest leaf */ > + *ebx = 0x61774d56; /* "VMwa" */ > + *ecx = 0x4d566572; /* "reVM" */ > + *edx = 0x65726177; /* "ware" */ > + break; > + > + case 0x1 ... 0xf: > + *eax = 0; /* Reserved */ > + *ebx = 0; /* Reserved */ > + *ecx = 0; /* Reserved */ > + *edx = 0; /* Reserved */ > + break; > + > + case 0x10: > + /* (Virtual) TSC frequency in kHz. */ > + *eax = d->arch.tsc_khz; > + /* (Virtual) Bus (local apic timer) frequency in kHz. */ > + *ebx = 1000000000ull / APIC_BUS_CYCLE_NS / 1000ull; At least 1 pair of brackets please, especially as the placement of brackets affects the result of this particular calculation. > + *ecx = 0; /* Reserved */ > + *edx = 0; /* Reserved */ > + break; > + > + default: > + return 0; > + } > + > + return 1; > +} > + > +/* > + * Local variables: > + * mode: C > + * c-file-style: "BSD" > + * c-basic-offset: 4 > + * tab-width: 4 > + * indent-tabs-mode: nil > + * End: > + */ > diff --git a/xen/arch/x86/traps.c b/xen/arch/x86/traps.c > index 10fc2ca..f353f42 100644 > --- a/xen/arch/x86/traps.c > +++ b/xen/arch/x86/traps.c > @@ -685,8 +685,12 @@ int cpuid_hypervisor_leaves( uint32_t idx, uint32_t sub_idx, > uint32_t *eax, uint32_t *ebx, uint32_t *ecx, uint32_t *edx) > { > struct domain *d = current->domain; > - /* Optionally shift out of the way of Viridian architectural leaves. */ > - uint32_t base = is_viridian_domain(d) ? 0x40000100 : 0x40000000; > + /* > + * Optionally shift out of the way of Viridian or VMware > + * architectural leaves. > + */ > + uint32_t base = is_viridian_domain(d) | is_vmware_domain(d) ? > + 0x40000100 : 0x40000000; Again, brackets please for binary operators. (We have had one recent slipup because of the precedence of | and ?:) Furthermore, I think you mean (is_viridian_domain(d) || is_vmware_domain(d)) ? 0x40000100 : 0x40000000; which allows for short circuiting of is_vmware_domain(). > uint32_t limit, dummy; > > idx -= base; > diff --git a/xen/include/asm-x86/hvm/hvm.h b/xen/include/asm-x86/hvm/hvm.h > index 1123857..546210a 100644 > --- a/xen/include/asm-x86/hvm/hvm.h > +++ b/xen/include/asm-x86/hvm/hvm.h > @@ -347,6 +347,9 @@ static inline unsigned long hvm_get_shadow_gs_base(struct vcpu *v) > #define is_viridian_domain(_d) \ > (is_hvm_domain(_d) && ((_d)->arch.hvm_domain.params[HVM_PARAM_VIRIDIAN])) > > +#define is_vmware_domain(_d) \ > + (is_hvm_domain(_d) && ((_d)->arch.hvm_domain.params[HVM_PARAM_VMWARE_HW])) > + > void hvm_hypervisor_cpuid_leaf(uint32_t sub_idx, > uint32_t *eax, uint32_t *ebx, > uint32_t *ecx, uint32_t *edx); > diff --git a/xen/include/asm-x86/hvm/vmware.h b/xen/include/asm-x86/hvm/vmware.h > new file mode 100644 > index 0000000..f254106 > --- /dev/null > +++ b/xen/include/asm-x86/hvm/vmware.h > @@ -0,0 +1,31 @@ > +/* > + * asm-x86/hvm/vmware.h > + * > + * Copyright (C) 2012 Verizon Corporation > + * > + * This file is free software; you can redistribute it and/or modify it > + * under the terms of the GNU General Public License Version 2 (GPLv2) > + * as published by the Free Software Foundation. > + * > + * This file is distributed in the hope that it will be useful, > + * but WITHOUT ANY WARRANTY; without even the implied warranty of > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU > + * General Public License for more details. . > + */ > + > +#ifndef ASM_X86_HVM_VMWARE_H__ > +#define ASM_X86_HVM_VMWARE_H__ #include (IIRC) please, or uint32_t could cause a compilation failure given specific orderings of #include's in translation units. ~Andrew > + > +int cpuid_vmware_leaves(uint32_t idx, uint32_t *eax, uint32_t *ebx, > + uint32_t *ecx, uint32_t *edx); > + > +#endif /* ASM_X86_HVM_VMWARE_H__ */ > + > +/* > + * Local variables: > + * mode: C > + * c-file-style: "BSD" > + * c-basic-offset: 4 > + * indent-tabs-mode: nil > + * End: > + */ > diff --git a/xen/include/public/hvm/params.h b/xen/include/public/hvm/params.h > index 614ff5f..dee6d68 100644 > --- a/xen/include/public/hvm/params.h > +++ b/xen/include/public/hvm/params.h > @@ -151,6 +151,9 @@ > /* Location of the VM Generation ID in guest physical address space. */ > #define HVM_PARAM_VM_GENERATION_ID_ADDR 34 > > -#define HVM_NR_PARAMS 35 > +/* Params for VMware */ > +#define HVM_PARAM_VMWARE_HW 35 > + > +#define HVM_NR_PARAMS 36 > > #endif /* __XEN_PUBLIC_HVM_PARAMS_H__ */