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 22:34:22 -0000
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>
Delivery-date: Wed, 23 Jan 2008 14:35:01 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1449F58C868D8D4E9C72945771150BDF02077246@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> <DD74FBB8EE28D441903D56487861CD9D275A024A@xxxxxxxxxxxxxxxxxxxxxx> <1449F58C868D8D4E9C72945771150BDF02077246@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AchdJLibYAsM6tf0TQmN0NytQtkgrAAFoN6AAAFwnhMAJGZRIAAK2VqAAAAk5aAABASFcA==
Thread-topic: [Xen-devel] [PATCH] Disable Xen PowerNow! support on Opteron 2nd gen and earlier processors
> Yes, I can regularly generate messages by switching the governor
> from powersave (minimum frequency) to performance (maximum
> frequency).
> 
> > How far is time stepping backwards?
> > ns, us, or ms?
> 
> Rolf's message is typical:
> > Jan 19 00:11:09 server kernel: printk: 14 messages suppressed.
> > Jan 19 00:11:09 server kernel: Timer ISR/0: Time went backwards:
> > delta=-123862858 delta_cpu=-123862858 shadow=
> > 2993571302800 off=705014593 processed=2994400167600
> cpu_processed=2994400167600
>
> It seems to happen most reliably when there's a large jump in
> frequency (2.6 GHz to 800 MHz or vice versa) but I've seen it
> happen for smaller switches.  Usually there's 1 large backward
> movement, and then 2-4 smaller ones.  It doesn't always happen,
> especially if there are multiple shifts in a short period (ie,
> constant changes on the ondemand governor) and it seems to
> happen more consistently when increasing frequency.

Increasing the frequency requires (1) instructing the regulator to
increasing the voltage, (2) waiting for it to settle, (3) increasing the
multipler, (4) wait for the PLL to settle, (5) unpause the CPU.

Which of these steps are under software control on PowerNow?  

Since we probably don't know how long we had to wait between when the
multipler was increased and when the CPU was un-paused, it will be
necessary to recalibrate the CPU to the global time source (PIT/HPET).

Ian







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

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