On Sun, Apr 07, 2013 at 01:38:48PM +0200, Jan Kiszka wrote: > On 2013-04-07 13:37, Gleb Natapov wrote: > > On Sun, Apr 07, 2013 at 01:33:05PM +0200, Jan Kiszka wrote: > >> On 2013-02-27 12:19, Gleb Natapov wrote: > >>> On Sat, Feb 23, 2013 at 05:05:29PM +0100, Jan Kiszka wrote: > >>>> From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx> > >>>> > >>>> This fixes boot lockups with "no-kvmclock", when the host is not > >>>> exposing this particular feature (QEMU: -cpu ...,-kvmclock) or when > >>>> the kvmclock initialization failed for whatever reason. > >>>> > >>>> Signed-off-by: Jan Kiszka <jan.kiszka@xxxxxxxxxxx> > >>> Applied, thanks. > >> > >> Just noticed that this fix isn't in Linus tree yet, thus also not yet in > >> 3.8.y. Which route does it take? > >> > > It is scheduled to go into 3.10. To get it into 3.8.y we need to send it > > to stable@. > > Hmm, it's a bug fix for an ugly early kernel crash... > It was not a regression introduced in 3.9 and this usually means that fix is delayed to the next merge window. Severe bugs with simple fix could be exceptions, and I probably misjudged this one. Note that the patch is for 3.9 would have helped to avoid that. As it stands the patch will go to 3.9 via stable. -- 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
