> -----Original Message----- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: Thursday, January 31, 2013 2:38 AM > To: KY Srinivasan > Cc: o...@aepfle.de; b...@alien8.de; a...@canonical.com; x...@kernel.org; > t...@linutronix.de; de...@linuxdriverproject.org; gre...@linuxfoundation.org; > jasow...@redhat.com; linux-kernel@vger.kernel.org; h...@zytor.com > Subject: RE: [PATCH 2/3] X86: Add a check to catch Xen emulation of Hyper-V > > >>> On 30.01.13 at 19:12, KY Srinivasan <k...@microsoft.com> wrote: > > Presumably, Hyper-V emulation is only to run enlightened Windows. The issue > > with > > Xen is not that it emulates Hyper-V, but this emulation is turned on while > > running Linux. > > That is the reason I chose to check for Xen. Would you prefer a DMI check > > for the Hyper-V > > platform. > > I consider DMI checks to be too fragile here - in particular with > the eventual passing through of host DMI attributes to guests, > this sets you up for mistakes. Instead, I would envision you > scanning the whole CPUID range "reserved" for virtualization > (starting at 0x40000000) and see whether you get back > anything other than the Hyper-V identification (much like the > way xen_cpuid_base() scans for the Xen range). Of course > that's under the premise that you're right in assuming Hyper-V > would never emulate any other hypervisor's interface.
Agreed; I will make the appropriate changes as you have recommended. Regards, K. Y -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
