From: Jeremy Katz Subject: RE: CONFIG_CPU_FREQ Date: Wed, 15 Feb 2006 14:14:49 -0500 Message-ID: <1140030889.12083.22.camel@bree.local.net> References: <907625E08839C4409CE5768403633E0B0EABF7@sefsexmb1.amd.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <907625E08839C4409CE5768403633E0B0EABF7@sefsexmb1.amd.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Petersson, Mats" Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Wed, 2006-02-15 at 15:10 +0100, Petersson, Mats wrote: > CPU frequency changing doesn't work under Xen at the moment, and it's > pretty pointless for individual kernels to do this without understanding > what else is going on in the OTHER kernels that may be running on the > system - so it makes sense to disable it by "permanent" measure, until > someone gets round to figuring out how to make Xen itself handle CPU > frequency changing (perhaps with help from Dom0)... I could be insane, but I'm pretty sure it works at least in dom0 right now. So disabling it across the board means a loss of functionality for anyone wanting to run dom0 on their laptop which isn't really needed. Having it dependent on either XEN_PHYSDEV_ACCESS or XEN_PRIVILEGED_GUEST, on the other hand, doesn't seem unreasonable Jeremy