From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ronald G Minnich Subject: Re: [Patch] time resolution fix. Date: Mon, 20 Mar 2006 08:55:40 -0700 Message-ID: <441ED07C.4050908@lanl.gov> References: <26F44F810A51DF42A127BC2A06BE185E03D651C2@pdsmsx404> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel Devel , "Dong, Eddie" , "Nakajima, Jun" List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > Well, freezing the TSC while a guest is descheduled is not very nice at > all, but I can imagine it stops you getting time went backwards messages > if you are also forcibly re-setting the TSC on PIT ticks. :-) I think freezing the TSC is probably a very bad idea for guests. I really do want to know what's going on. > In summary, I'm not sure about this patch. I feel that if I take it I'm > encouraging 'onward and upward' development without spending the time to > make sure fundamental abstractions like time are designed and > implemented soundly. I think you should heed your intuition ... it's usually quite solid! thanks ron