search for: extcnl

...line option and dom0 CONFIG_CPU_FREQ are two conditions to enable xen controlled cpufreq. When FREQCTL_xen is set, cpufreq driver/governor within xen is enabled, which however doesn''t start working until someone (dom0) notifies xen about processor freq info. When dom0 CPU_FREQ is enabled, extcnl logic then attempts to parse ACPI px info and then notify Xen by hypercall. After that, Xen cpufreq begins working. I think we may enable CPU_FREQ in dom0''s config by default, to eliminate such disconnected logic. > >>>admit that while I didn''t try it, I suspect it...

Now that I finally got around to update our sources, I had a closer look at those changes, and apart from stylistic issues on the Linux side (part of which I may have asked for, but the result was somewhat overdone so the code is hardly legible now - I''ve got a patch queued to streamline this a little) I find it rather odd (fragile) that the who-is-in-charge information gets propagated