From: "Jan Beulich" Subject: [PATCH] i386 linux: RE: CONFIG_CPU_FREQ Date: Wed, 15 Feb 2006 16:49:36 +0100 Message-ID: <43F35BA0.76F0.0078.0@novell.com> References: <907625E08839C4409CE5768403633E0B0EABF7@sefsexmb1.amd.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=__Part1537A880.0__=" 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: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. --=__Part1537A880.0__= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Patch conditionalizing the option attached. >>> "Petersson, Mats" 15.02.06 15:10:55 >>> > -----Original Message----- > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of > Jan Beulich > Sent: 15 February 2006 14:06 > To: xen-devel@lists.xensource.com > Subject: [Xen-devel] CONFIG_CPU_FREQ > > I see that linux-defconfig-xen{,0}_x86_32 have > CONFIG_CPU_FREQ disabled, presumably since these are not > expected to work (and in fact some of the resulting modules > don't have all the symbols they depend upon available). Can > someone confirm this? We have this and the dependent options > still enabled in our SLES10 kernels, and I'd like to know > whether I should try to fix the missing symbols problem, or > whether instead CPU_FREQ should be made dependent upon > !X86_XEN (similar to how x86-64 does). > > Thanks, Jan > 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)... -- Mats _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --=__Part1537A880.0__= Content-Type: text/plain; name="xenlinux-i386-kconfig-no-cpu_freq.patch" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="xenlinux-i386-kconfig-no-cpu_freq.patch" Index: head-2006-02-14/arch/i386/Kconfig =================================================================== --- head-2006-02-14.orig/arch/i386/Kconfig 2006-02-13 15:07:48.000000000 +0100 +++ head-2006-02-14/arch/i386/Kconfig 2006-02-15 16:30:32.000000000 +0100 @@ -946,7 +946,9 @@ config APM_REAL_MODE_POWER_OFF endmenu +if !X86_XEN source "arch/i386/kernel/cpu/cpufreq/Kconfig" +endif endmenu --=__Part1537A880.0__= Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --=__Part1537A880.0__=--