From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Wang Subject: Re: [PATCH 4/4] x86: properly handle kvm emulation of hyperv Date: Thu, 25 Jul 2013 16:12:49 +0800 Message-ID: <51F0DE01.50607@redhat.com> References: <1374572465-15278-1-git-send-email-jasowang@redhat.com> <1374572465-15278-4-git-send-email-jasowang@redhat.com> <51EE97BD.4050402@zytor.com> <51EF59FB.8040207@redhat.com> <51EF5C9C.6070403@zytor.com> <51EF7A2A.6040003@redhat.com> <51EF7CFB.8030104@redhat.com> <889e20ee-7655-4fdc-b30a-150b8604ca0f@email.android.com> <51F0DAD1.8080108@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: "H. Peter Anvin" , KY Srinivasan , "tglx@linutronix.de" , "mingo@redhat.com" , "x86@kernel.org" , "gleb@redhat.com" , "kvm@vger.kernel.org" , "linux-kernel@vger.kernel.org" To: Paolo Bonzini Return-path: In-Reply-To: <51F0DAD1.8080108@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 07/25/2013 03:59 PM, Paolo Bonzini wrote: > Il 24/07/2013 23:37, H. Peter Anvin ha scritto: >> What I'm suggesting is exactly that except that the native hypervisor is later in CPUID space. > Me too actually. > > I was just suggesting an implementation of the idea (that takes into > account hypervisors detected by other means than CPUID). > > Paolo This make sense, will send V2. Thanks >> KY Srinivasan wrote: >>> As Paolo suggested if there were some priority encoded, the guest could make an >>> informed decision. If the guest under question can run on both hypervisors A and B, >>> we would rather the guest discover hypervisor A when running on A and >>> hypervisor B when running on B. The priority encoding could be as simple as >>> surfacing the native hypervisor signature earlier in the CPUID space.