From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: [PATCH][v4] PV extension of HVM(hybrid) support in Xen Date: Mon, 01 Mar 2010 17:49:55 -0800 Message-ID: <4B8C6EC3.2020307@goop.org> References: <201003011743.41341.sheng@linux.intel.com> <20100301102127.GA17243@whitby.uk.xensource.com> <201003011940.50685.sheng@linux.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: <201003011940.50685.sheng@linux.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: Sheng Yang Cc: Ian Campbell , Ian Pratt , xen-devel , Tim Deegan , Keir Fraser List-Id: xen-devel@lists.xenproject.org On 03/01/2010 03:40 AM, Sheng Yang wrote: > The issue is pv timer. It assumed the tsc start from 0, which is different > from HVM. So I'd like to give it a explicit call here. Otherwise it can be > hooked in evtchn binding, but I don't think that's clear... > > [...] >> Only vcpu 0? Doesn't this do horrible things to timekeeping in the guest? >> > The other vcpus are initialized when it is brought up. TSC started from 0 is a > fundamental assumption for pv clock in Linux... > Could you expand on this? Do you mean in the pvops Xen time code? What do you mean? J