From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mark McLoughlin <markmc@redhat.com>
Subject: Re: KVM: x86: disable kvmclock on non constant TSC hosts
Date: Thu, 12 Feb 2009 14:33:56 +0000
Message-ID: <1234449236.3707.72.camel@blaa>
References: <20090210172407.GA31394@amt.cnet>
	 <20090210225945.GA5373@amt.cnet> <4992BE30.6030009@redhat.com>
	 <1234382903.14052.246.camel@blaa> <20090211225543.GA15230@amt.cnet>
	 <4993F3AA.9080800@redhat.com>
Reply-To: Mark McLoughlin <markmc@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	Glauber de Oliveira Costa <gcosta@redhat.com>,
	kvm-devel <kvm@vger.kernel.org>, Chris Wright <chrisw@redhat.com>
To: Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx2.redhat.com ([66.187.237.31]:46993 "EHLO mx2.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752060AbZBLOeB (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 12 Feb 2009 09:34:01 -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 n1CEY0CY027339
	for <kvm@vger.kernel.org>; Thu, 12 Feb 2009 09:34:00 -0500
In-Reply-To: <4993F3AA.9080800@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Thu, 2009-02-12 at 12:02 +0200, Avi Kivity wrote:
> Marcelo Tosatti wrote:
> > 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.

I'm not really following Marcelo here ...

> Does 'Cc: stable' mean -stable picks it up automatically?  That doesn't 
> seem right.

Yeah, I think if you CC: stable it gets pulled into the stable queue by
scripts once linus merges it.

Cheers,
Mark.