From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincent Hanquez Subject: Re: [PATCH] xl: tsc_mode parameter in guest configuration file Date: Tue, 30 Mar 2010 09:15:04 +0100 Message-ID: <4BB1B308.4040209@eu.citrix.com> References: <446767b3-2fdf-493f-9947-b5c57d70d556@default> <4BB0CAAB.4060404@eu.citrix.com 1269887531.28673.3.camel@eric.cam.xci-test.com> <42f1bd27-03fd-4b5d-a465-35bbe7b388fa@default> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <42f1bd27-03fd-4b5d-a465-35bbe7b388fa@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: "Eric Chanudet (Intern)" , xen-devel List-Id: xen-devel@lists.xenproject.org On 29/03/10 20:49, Dan Magenheimer wrote: > Thanks Eric! > > Sorry I didn't mention this earlier, but I just remembered it. > > For some of the tsc_mode's to work properly, tsc_mode AND > additional tsc information must be preserved across a > save/restore/migration. Also, the no_migrate config option has > an indirect impact on tsc_mode; with no_migrate specified > certain guests will be able to use tsc as their primary > clocksource, which can be much faster. (IOW, implementing > no_migrate is not a requirement, but may be worthwhile.) it seems that the tsc information are automatically save by xenguest saving code, and embedded in the save image. -- Vincent