From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: A clocksource question
Date: Fri, 12 Mar 2010 13:24:54 -0800
Message-ID: <4B9AB126.1070406@goop.org>
References: <4B962748.90609@invisiblethingslab.com>
	<4B96DB69.10101@goop.org	4B981997.4030605@invisiblethingslab.com>
	<56cc3abf-21f6-4178-b00e-0331538080d9@default>
	<4FA716B1526C7C4DB0375C6DADBC4EA3554D53F1B0@LONPMAILBOX01.citrite.net>
	<4B983EC9.2030105@invisiblethingslab.com>
	<4B98421F.7040102@goop.org>
	<4B984533.9030402@invisiblethingslab.com>
	<4B9877CA.4060204@goop.org>
	<4B998A70.3050500@invisiblethingslab.com>
	<4B998F9A.3040706@goop.org>
	<4B998CE9.2030704@invisiblethingslab.com>
	<4B9A8FDE.8070506@invisiblethingslab.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4B9A8FDE.8070506@invisiblethingslab.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Joanna Rutkowska <joanna@invisiblethingslab.com>
Cc: Ian Pratt <Ian.Pratt@eu.citrix.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, Dan Magenheimer <dan.magenheimer@oracle.com>
List-Id: xen-devel@lists.xenproject.org

On 03/12/2010 11:02 AM, Joanna Rutkowska wrote:
> Today I upgraded to xen 3.4.3-rc3 and tried the 2.6.32 kernel (the
> Micheal Young's one) -- the same problem :(
>    

Good, in a way.  I can't think of a reason it would change from .31 -> .32.

Experiment of the moment: does changing the clocksource in 
/sys/devices/system/clocksource/clocksource0/current_clocksource reset 
the problem after killing the other domains?  Ie, switch it from 
xen->jiffies->xen for a while.

Thanks,
     J