On Fri, Jan 25, KY Srinivasan wrote: > My fear is that there is no guarantee that Xen would not emulate this > feature in the spirit of making Hyper-V emulation "more" complete. > Since all this problem is because Xen thinks it is running a viridian > domain (when in fact it is running Linux), I felt we should explore > why the viridian tag got set for a Linux VM. If we can fix that we > would have a solution that does not depend upon assuming that Xen > would not emulate a particular Hyper-V feature.
In my opinion this logic is backwards. A host provides a set of functionality/features to a given guest, no matter what runs inside the guest. And the guest can query the feature list and configure itself accordingly. In this specific case the guest finds feature A (the cpuid result) and expects that feature B (a clock source) is present as well, even if feature B has its very own availability flag. Maybe I miss your point. Olaf -- 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/
