public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark McLoughlin <markmc@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	Glauber de Oliveira Costa <gcosta@redhat.com>,
	kvm-devel <kvm@vger.kernel.org>, Chris Wright <chrisw@redhat.com>
Subject: Re: KVM: x86: disable kvmclock on non constant TSC hosts
Date: Thu, 12 Feb 2009 14:33:56 +0000	[thread overview]
Message-ID: <1234449236.3707.72.camel@blaa> (raw)
In-Reply-To: <4993F3AA.9080800@redhat.com>

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.


  reply	other threads:[~2009-02-12 14:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10 17:24 KVM: x86: disable kvmclock on non constant TSC hosts Marcelo Tosatti
2009-02-10 22:59 ` Marcelo Tosatti
2009-02-11 12:01   ` Avi Kivity
2009-02-11 20:08     ` Mark McLoughlin
2009-02-11 22:55       ` Marcelo Tosatti
2009-02-12 10:02         ` Avi Kivity
2009-02-12 14:33           ` Mark McLoughlin [this message]
2009-02-12 16:29           ` Chris Wright
2009-02-12 16:35             ` Avi Kivity
2009-02-12 16:39               ` Chris Wright
2009-02-12 17:54                 ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1234449236.3707.72.camel@blaa \
    --to=markmc@redhat.com \
    --cc=avi@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=gcosta@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox