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: John Levon <levon@xxxxxxxxxxxxxxxxx>, "Stephen C. Tweedie" <sct@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Disable Xen PowerNow! support on Opteron 2nd gen and earlier processors
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 25 Jan 2008 18:18:15 +0000
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Langsdorf, Mark" <mark.langsdorf@xxxxxxx>
Delivery-date: Fri, 25 Jan 2008 10:18:54 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080125174615.GA26219@xxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Achffqbb5T53TstxEdyNUQAWy6hiGQ==
Thread-topic: [Xen-devel] [PATCH] Disable Xen PowerNow! support on Opteron 2nd gen and earlier processors
User-agent: Microsoft-Entourage/11.3.6.070618
On 25/1/08 17:46, "John Levon" <levon@xxxxxxxxxxxxxxxxx> wrote:

> On Fri, Jan 25, 2008 at 05:19:53PM +0000, Stephen C. Tweedie wrote:
> 
>>> Seeing them at that frequency (less than one a minute) is not too serious.
>>> Perhaps we should get rid of the message, or reduce its priority.
>> 
>> They are most definitely serious --- gettimeofday() going backwards
>> breaks Unix semantics.  It breaks applications.  It _will_ corrupt
>> application data --- things like database rollback logs that rely on
>> timestamp monotonicity to order things correctly will break.
> 
> I thought Linux now enforced a monotonic clock the same way we were
> forced to - that is, globally synchronise and make sure we return last
> value + 1, even when the Xen clock goes backwards across CPUs, which it
> does regularly, powernow or not?

This is also true. Although in this case the backwards deltas of >100ms are
a bit extreme and will cause application-visible progress of time to stall
for that length of time. We've suggested some leads for Mark to look into,
so hopefully that will improve matters. Ultimately, the work being done to
put the C/P-state governors in Xen is the better approach, once that's
ready.

 -- Keir



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

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