From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: A clocksource question Date: Fri, 12 Mar 2010 15:48:45 -0800 Message-ID: <4B9AD2DD.90907@goop.org> References: <4B962748.90609@invisiblethingslab.com> <4B9A8FDE.8070506@invisiblethingslab.com> <4B9AB126.1070406@goop.org> <201003122256.02254.tobias.geiger@vido.info> <4B9AB9FE.8070601@goop.org> <4B9AABB9.7030906@invisiblethingslab.com> <4B9AAE6A.6050801@invisiblethingslab.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4B9AAE6A.6050801@invisiblethingslab.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: Joanna Rutkowska Cc: Tobias Geiger , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 03/12/2010 01:13 PM, Joanna Rutkowska wrote: > >> The "clocksource tsc unstable" messages trouble me too BTW. They seem to >> appear before the hrtimer "interrupt too slow" messages. >> >> > But this "tsc unstable" message does not seem to be so critical, They're nothing to worry about. > e.g. I > just started my system (xen clocksource) and started a VM, and got the > usual hrtimer "slow interrupt" warning, and then all the symptoms > started, but there no "tsc unstables" warning in dmesg. > > However, I previously missed another message, that seem to occur at the > very beginning of the system life (before I started any other VMs): > > Marking TSC unstable due to TSC halts in idle > That doesn't matter because it doesn't use the tsc clocksource. The Xen clocksource uses the tsc hardware register, but it isn't subject to the same constraints that the tsc clocksource is. The tsc clocksource calibration is probably getting confused by being on a vcpu. J