From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [RFC] Physical hot-add cpus and TSC Date: Fri, 28 May 2010 18:19:02 +0100 Message-ID: References: <681ea80b-75c6-41cc-a13d-3c7e25721f99@default> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <681ea80b-75c6-41cc-a13d-3c7e25721f99@default> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Magenheimer , "Jiang, Yunhong" , "Xen-Devel (xen-devel@lists.xensource.com)" , Ian Pratt List-Id: xen-devel@lists.xenproject.org On 28/05/2010 17:36, "Dan Magenheimer" wrote: >> Anyhow, retreading this argument is not going to be fruitful >> It's fair to >> say that your definition is now also Xen's definition. > > Sorry, I'm not trying to beat a dead horse. I'm just > playing whack-a-mole and repeating arguments for a > new audience and a new corner case. If you prefer, I > can take that offlist. No, that's fine. And in general, supporting both the consistent-TSC and fast-TSC cases (the latter including perhaps a more-Xen-features subcase as well) as configurable options is good. Those who care will know how they want to set the options. -- Keir