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

[Xen-devel] CONFIG_CPU_FREQ

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] CONFIG_CPU_FREQ
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Wed, 15 Feb 2006 15:05:57 +0100
Delivery-date: Wed, 15 Feb 2006 14:17:11 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
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

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

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