WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] [PATCH] Disable Xen PowerNow! support on Opteron 2nd gen

To: "Langsdorf, Mark" <mark.langsdorf@xxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] Disable Xen PowerNow! support on Opteron 2nd gen and earlier processors
From: "Ian Pratt" <Ian.Pratt@xxxxxxxxxxxxx>
Date: Wed, 23 Jan 2008 20:27:59 -0000
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>
Delivery-date: Wed, 23 Jan 2008 12:28:33 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1449F58C868D8D4E9C72945771150BDF0207723C@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <DD74FBB8EE28D441903D56487861CD9D273ABB3D@xxxxxxxxxxxxxxxxxxxxxx> <C3BC15F7.12AEA%Keir.Fraser@xxxxxxxxxxxx> <1449F58C868D8D4E9C72945771150BDF0207723C@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AchdJLibYAsM6tf0TQmN0NytQtkgrAAFoN6AAAFwnhMAJGZRIAAK2VqA
Thread-topic: [Xen-devel] [PATCH] Disable Xen PowerNow! support on Opteron 2nd gen and earlier processors
> > Yes, and that is already done, hooked off the cpu notifier
> > callback chain.
> > Nobbling the C- and P-state logic shouldn't be necessary.
> 
> And yet, people are still reporting "Time went backwards"
> messages upwards of 30-40 times an hour on RevF Opterons
> when PowerNow! is enabled on Xen.
> 
> I spent a month trying to debug this and I made no significant
> progress.  If someone who understands Xen timekeeping wants to
> help me dive into this, I'll be glad to take another stab at
> it.  As it is, even with informing Xen of frequency changes,
> Xen does not ensure monotinicity.

I do think we need to understand what's going on here.

Are the 'time went backwards' messages correlated with power management
operations? How far is time stepping backwards? ns, us, or ms? 

Are you sure the systems aren't overheating and performing emergency
T-state thermal throttling?  

Ian





_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>