From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [RFC] Physical hot-add cpus and TSC Date: Wed, 26 May 2010 16:45:49 +0100 Message-ID: References: <3c6e0679-a0b8-42ae-9e86-36e7fa260e73@default> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <3c6e0679-a0b8-42ae-9e86-36e7fa260e73@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 , "Xen-Devel (xen-devel@lists.xensource.com)" List-Id: xen-devel@lists.xenproject.org On 26/05/2010 16:19, "Dan Magenheimer" wrote: > Much of the TSC-based time infrastructure in Xen, > especially as exposed to guests, is rather sensitive > to sudden dramatic differences in TSC values between > physical processors. Hot-add of physical CPUs will > introduce a huge difference. True at the moment, but can we not just whack the TSC of the newly added CPU on the head when it is brought online, to match the boot CPU? I think that would suffice for systems with 'reliable tsc' which are the only ones we don't emulate tsc by default? -- Keir