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@lists.xensource.com
http://lists.xensource.com/xen-devel
> -----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
Patch conditionalizing the option attached.>>> "Petersson, Mats" <Mats.Petersson@amd.com> 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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 2/15/06, Jeremy Katz <katzj@redhat.com> wrote:> 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 unreasonableIt is already dependent on !XEN_UNPRIVILEGED_GUEST on i386, I''ve changed x86_64 to match. christian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel