Re: [Xen-devel] RE: Xen 3.4 / cpufreq=dom0-kernel / ondemand govenor doesn't step

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

On 01/06/2009 04:52, "Liu, Jinsong" <jinsong.liu@xxxxxxxxx> wrote:

> Actually xen cpufreq default option is 'cpufreq=xen', means xen hypervisor
> will take charge of cpufreq logic, you can try this option.
> 'cpufreq=dom0-kernel' means dom0 will take charge of cpufreq logic, but this
> part was not maintained by me.
> 
> http://xenbits.xensource.com/xen-unstable.hg?rev/674e4d43955f is not related
> to 'cpufreq=dom0-kenrel' option.
> 
> If you use 'cpufreq=xen', you can set cpufreq para (governor, speed,
> sampling-rate, threshold, etc.) by grub cmdline at booting time, or by xenpm
> tools at runtime.
> currently xenpm tools implement all para same as you can get&set from native
> linux /sys/devices/system/cpu/cpux/cpufreq interface.

...and if you want to pursue cpufreq=dom0-kernel further, Mark Langsdorf is
the person to contact. You can find his email address in the changelogs and
in the list archives, no doubt.

 -- Keir



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