On Mon, Feb 11, 2013 at 07:05:50PM +0100, Jan Kiszka wrote: > >>> thus 3.0. We are running on such a 3.0.x host kernel (SLES11.2), and > >>> this issue only triggers on specific hosts with specific guest > >>> configurations. After no longer seeing it with kvm/next, I bisected the > >>> fix to this commit and instrumented it to ensure the case was actually hit. > >>> > >> I see. Too later to try and push it to 3.8 now, will queue for stable. Not > >> sure if 3.0 is still maintained by stable folks though. > >> > > And just after I wrote that 3.0.63 was announced. > > Well, if you consider pushing it that far, an adapted version will be > needed. For us, it is not that important as we already have to patch kvm > down there due to missing f1c1da2bde (SVM: Keep intercepting task > switching with NPT enabled). > OK, no reason to push it that far then. -- Gleb. -- 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
