Subject: Re: + paravirt-vmi-timer-patches.patch added to -mm tree
From: Daniel Walker <dwalker@mvista.com>
To: Zachary Amsden <zach@vmware.com>
Cc: linux-kernel@vger.kernel.org, ak@suse.de, chrisw@sous-sol.org,
       jeremy@xensource.com, rusty@rustcorp.com.au
In-Reply-To: <45A00878.1000705@vmware.com>
References: <200612152227.kBFMRNuQ002977@shell0.pdx.osdl.net>
	 <1168106760.26086.222.camel@imap.mvista.com>  <45A00878.1000705@vmware.com>
Content-Type: text/plain
Date: Sat, 06 Jan 2007 12:40:57 -0800
Message-Id: <1168116057.26086.227.camel@imap.mvista.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 770
Lines: 21

On Sat, 2007-01-06 at 12:37 -0800, Zachary Amsden wrote:

> >
> > There is already a dynamic tick (NO_HZ) system in the -mm tree .. Given
> > that this implementation seems unnecessary. Why do you need another
> > different system to do this?
> >   
> 
> We don't.  This was written before the dynamic tick code, and now they 
> need to be merged.  Until then, they can safely coexist.

So really this can't go upstream till that merge happens. What's
preventing you from just directly using NO_HZ without changes?

Daniel  

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/