From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH] x86: kvmclock: Do not setup kvmclock vsyscall in the
 absence of that clock
Date: Sun, 7 Apr 2013 14:37:09 +0300
Message-ID: <20130407113709.GQ17919@redhat.com>
References: <5128E8C9.1050000@web.de>
 <20130227111955.GC23616@redhat.com>
 <51615971.9050604@web.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
To: Jan Kiszka <jan.kiszka@web.de>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:7461 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S933278Ab3DGLhM (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sun, 7 Apr 2013 07:37:12 -0400
Content-Disposition: inline
In-Reply-To: <51615971.9050604@web.de>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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@siemens.com>
> >>
> >> 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@siemens.com>
> > 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@.

--
			Gleb.