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@xxxxxxxxxxxxx> 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. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
