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

Re: [Xen-devel] CONFIG_CPU_FREQ change

  • To: "Jan Beulich" <JBeulich@xxxxxxxxxx>
  • From: "Christian Limpach" <christian.limpach@xxxxxxxxx>
  • Date: Mon, 20 Feb 2006 18:12:30 +0000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 20 Feb 2006 18:25:42 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BlR8zCnvLfwnqC54YzRTtKaXXxyrrWH8jDSCpBJXJoyOVqzJVo/vjtGHtgl48fFTmGgcCIEszlaC3JWTaLF0Xt4du2x/1FrKIhq27gd1+SPsjnp+HGsxMOQU6KGELRpBMfXYSQ9/Q3sPgIzqw2leD7weWgLj+gjytAIne2nfFn4=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 2/20/06, Jan Beulich <JBeulich@xxxxxxxxxx> wrote:
> To my surprise, c/s 8888 enables CPU_FREQ for x86-64 rather than disabling it 
> for i386. Did anyone at your end actually
> test that if enabled this at least builds properly now? Not to mention that 
> of course this also should work... If I
> remember right, the main reason for posting a patch to disable it on 32-bits 
> (similar to how it was on 64-bits before)
> was that there were some missing symbols, and I don't think I saw any 
> changesets addressing this. Also, from previous
> discussion I seem to recall that it was generally agreed that there is little 
> point in allowing a single domain (even
> dom0) to decide whether/what power management actions should be taken without 
> knowing about the requirements of the rest
> of the system...

I went with the final statement in the thread where you posted the
patch, from Jeremy Katz stating, that it was working for dom0 and that
disabling it would remove functionality.  It is disabled for
unprivileged guests.  I'm happy to disable it entirely, if it doesn't
build or if it doesn't work.


Xen-devel mailing list



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