From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Live migration fails due to c/s 20627 Date: Tue, 15 Dec 2009 22:19:11 -0800 Message-ID: <4B287BDF.8020308@goop.org> References: <562bba8c-64a3-4876-b0ff-ae9349c76d3c@default> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <562bba8c-64a3-4876-b0ff-ae9349c76d3c@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 Cc: xen-devel@lists.xensource.com, kurt.hackel@oracle.com, "Dugger, Donald D" , "Xu, Dongxiao" , Keir Fraser , "Nakajima, Jun" , "Zhang, Xiantao" List-Id: xen-devel@lists.xenproject.org On 12/15/2009 08:14 PM, Dan Magenheimer wrote: > My argument is simply that if TSC_AUX cannot ALWAYS > be trusted by an application, apps will NEVER trust it. > And if apps NEVER trust it, why expose it at all? > The cpu/node info is only of heuristic value anyway; it is never trustworthy in an absolute sense. Apps just use it to try to optimise their own memory allocation and use patterns, but they can't rely on that info for actual correctness. J