From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] Adjust time init sequence Date: Thu, 11 Dec 2008 09:04:39 +0000 Message-ID: References: <0A882F4D99BBF6449D58E61AAFD7EDD603BB491F@pdsmsx502.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <0A882F4D99BBF6449D58E61AAFD7EDD603BB491F@pdsmsx502.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: "Tian, Kevin" , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 11/12/2008 00:47, "Tian, Kevin" wrote: > I guess not, due to same reason as why I sent out 1st patch idle > vcpu state entry. The point is the current TSC value, which count > from power on and is translated to a dozens of seconds for elapsed > time upon a zero tsc stamp. :-( I didn't realize that point in the start... Ah, because it's set up in early_time_init(). By the way, instead of avoiding NOW() early on, could we just set local_tsc_stamp in early_time_init()? Then we could use NOW() when initialising idle VCPUs, and also early on in init_xen_time()? We could set stime_platform_stamp = NOW() too, so that platform time is kicked off following BP's time. I could send a patch which I find tasteful if you think this could work? :-) -- Keir