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 09:12:00 -0800 Message-ID: <4B27C360.7080906@goop.org> References: <6CADD16F56BC954D8E28F3836FA7ED7105AC8685A3@shzsmsx501.ccr.corp.intel.com> <6CADD16F56BC954D8E28F3836FA7ED7105AC868872@shzsmsx501.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <6CADD16F56BC954D8E28F3836FA7ED7105AC868872@shzsmsx501.ccr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Xu, Dongxiao" Cc: Dan Magenheimer , "xen-devel@lists.xensource.com" , "kurt.hackel@oracle.com" , "Dugger, Donald D" , Keir Fraser , "Nakajima, Jun" , "Zhang, Xiantao" List-Id: xen-devel@lists.xenproject.org On 12/15/09 08:10, Xu, Dongxiao wrote: >> Why not just add the code to do rdtscp emulation, >> which would NOT break live migration? >> > Add rdtscp emulation has such problem that, in Intel VMX, the > vmexit control for rdtsc and rdtscp is the same, so if we trap > rdtscp for emulation, OS will suffer from looooots of rdtsc vmexit, > which will bring performance downgrade. > I don't see why that's relevant. In the case where you've migrated the domain, if the CPU has rdtsc but not rdtscp, won't the rdtscp vmexit with an illegal instruction trap? In that case you can emulate rdtscp while still having direct execution of rdtsc. Of course, having a wide difference between rdtscp and rdtsc performance may cause its own set of problems. J