From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: KVM: x86: disable kvmclock on non constant TSC hosts Date: Wed, 11 Feb 2009 20:55:43 -0200 Message-ID: <20090211225543.GA15230@amt.cnet> References: <20090210172407.GA31394@amt.cnet> <20090210225945.GA5373@amt.cnet> <4992BE30.6030009@redhat.com> <1234382903.14052.246.camel@blaa> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Avi Kivity , Glauber de Oliveira Costa , kvm-devel , Chris Wright To: Mark McLoughlin Return-path: Received: from mx2.redhat.com ([66.187.237.31]:34429 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755085AbZBKW4J (ORCPT ); Wed, 11 Feb 2009 17:56:09 -0500 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n1BMu9x0030377 for ; Wed, 11 Feb 2009 17:56:09 -0500 Content-Disposition: inline In-Reply-To: <1234382903.14052.246.camel@blaa> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, Feb 11, 2009 at 08:08:23PM +0000, Mark McLoughlin wrote: > On Wed, 2009-02-11 at 14:01 +0200, Avi Kivity wrote: > > Marcelo Tosatti wrote: > > > This is better. > > > > > > Currently, this code path is posing us big troubles, > > > and we won't have a decent patch in time. So, temporarily > > > disable it. > > > > > > > > > > Applied to master and kvm-updates/2.6.29, thanks. > > Should we add: > > Cc: stable@kernel.org I suppose Avi prefers the master->stable route so it can get autotested? But some sort of flag in the commit, like "Stable:Y" would help. Could setup a robot to monitor kvm-commits and maintain kvm-updates/2.6.2current (the queue to Linus), with human intervention when necessary. Then autotest can run continuously on that.