[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:41:00 +0000
  • Delivery-date: Wed, 23 Jan 2008 07:41:51 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AchdJLibYAsM6tf0TQmN0NytQtkgrAAFoN6AAAFwnhMAJGZRIAAAb3BSAAAbrbAAAGWEjw==
  • Thread-topic: [Xen-devel] [PATCH] Disable Xen PowerNow! support on Opteron 2nd gen and earlier processors

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



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