[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] Disable Xen PowerNow! support on Opteron 2nd gen and earlier processors


  • To: "Langsdorf, Mark" <mark.langsdorf@xxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Wed, 23 Jan 2008 15:26:33 +0000
  • Delivery-date: Wed, 23 Jan 2008 07:27:02 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AchdJLibYAsM6tf0TQmN0NytQtkgrAAFoN6AAAFwnhMAJGZRIAAAb3BS
  • Thread-topic: [Xen-devel] [PATCH] Disable Xen PowerNow! support on Opteron 2nd gen and earlier processors

On 23/1/08 15:17, "Langsdorf, Mark" <mark.langsdorf@xxxxxxx> wrote:

>> 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.

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.

 -- Keir



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.