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>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Disable Xen PowerNow! support on Opteron 2nd gen and earlier processors
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 23 Jan 2008 15:41:00 +0000
Delivery-date: Wed, 23 Jan 2008 07:41:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1449F58C868D8D4E9C72945771150BDF0207723D@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AchdJLibYAsM6tf0TQmN0NytQtkgrAAFoN6AAAFwnhMAJGZRIAAAb3BSAAAbrbAAAGWEjw==
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 23/1/08 15:31, "Langsdorf, Mark" <mark.langsdorf@xxxxxxx> 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.
> 
> Red Hat engineering is requesting the disable because they've
> gotten STREAM results with the test finishing before it started.
> 
> For myself, I don't mind the frequency of the messages.  In the
> real world, it's serious, especially on financial servers.

Firstly, Red Hat can apply this patch to their own tree, regardless of
whether or not it's in 2.6.18-xen.hg. Secondly, the cpufreq stuff only kicks
in if you put cpufreq=dom0-kernel on the Xen command line. Perhaps they
shouldn't do that? They could even omit it dynamically at install time,
based on install-hardware configuration.

 -- Keir



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

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