Il 07/09/2012 17:47, Stefan Bader ha scritto: > > Legacy hypervisors (RHEL 5.0 and RHEL 5.1) do not handle guest writes to > cr4 gracefully. If a guest attempts to write a bit of cr4 that is > unsupported, then the HV is so offended it crashes the domain. While > later guest kernels (such as RHEL6) don't assume the HV supports all > features, they do expect nicer responses. That assumption introduced > code that probes whether or not xsave is supported early in the boot. So > now when attempting to boot a RHEL6 guest on RHEL5.0 or RHEL5.1 an early > crash will occur. > > This patch is quite obviously an undesirable hack. The real fix for this > problem should be in the HV, and is, in later HVs. However, to support > running on old HVs, RHEL6 can take this small change. No impact will > occur for running on any RHEL HV (not even RHEL 5.5 supports xsave). > There is only potential for guest performance loss on upstream Xen. > > All this by way of explanation for why is this patch not going upstream.
If it is just 5.0 and 5.1, you can restrict the patch to Xen 3.0. 5.2 switched to Xen 3.1, which has been subsequently patched to death without rebasing. Paolo -- 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/
