From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: RE: Xen 3.4 / cpufreq=dom0-kernel / ondemand govenor doesn't step Date: Mon, 01 Jun 2009 08:47:57 +0100 Message-ID: References: <706158FABBBA044BAD4FE898A02E4BC201BD6618E5@pdsmsx503.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC201BD6618E5@pdsmsx503.ccr.corp.intel.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: "Liu, Jinsong" , Carsten Schiers , xen-devel List-Id: xen-devel@lists.xenproject.org On 01/06/2009 04:52, "Liu, Jinsong" 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