Messages in this thread | | | Date | Thu, 25 Jul 2013 16:12:49 +0800 | From | Jason Wang <> | Subject | Re: [PATCH 4/4] x86: properly handle kvm emulation of hyperv |
| |
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 <kys@microsoft.com> 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.
| |