From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Weekes Subject: Re: Performance difference between Xen versions Date: Mon, 02 May 2011 12:16:22 -0700 Message-ID: <4DBF0306.8040000@nuclearfallout.net> References: <4DBE41C9.1010409@ts.fujitsu.com> <4DBE7819020000780003F1B6@vpn.id2.novell.com> <4DBEEF6D.8080204@nuclearfallout.net> <20110502181222.GB7498@dumpdata.com> <4DBEFB6E.4090201@nuclearfallout.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4DBEFB6E.4090201@nuclearfallout.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: winston.l.wang@intel.com, "xen-devel@lists.xensource.com" , mark.langsdorf@amd.com, gang.wei@intel.com List-Id: xen-devel@lists.xenproject.org On 5/2/2011 11:43 AM, John Weekes wrote: > > The important thing that I missed on my end was not having the ACPI > processor driver selected (for some reason). I had cpufreq and ACPI > enabled, but I needed that, as well. cpufreq seems to be working now, as is xenpm (and using xenpm is much easier than setting the Xen command line), but I'm still not seeing signs that turbo mode is bumping up my CPU speed beyond the standard value, as I would expect it to. Here's what it looks like when I start a single process that spins and gobbles down a core: # xenpm get-cpufreq-states | grep current current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 2268 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz current frequency : 1600 MHz And looking at the core when running at the higher speed, I see: # xenpm get-cpufreq-para 5 cpu id : 5 affected_cpus : 5 cpuinfo frequency : max [2268000] min [1600000] cur [2268000] scaling_driver : acpi-cpufreq scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : *2268000 2267000 2133000 2000000 1867000 1733000 1600000 scaling frequency : max [2268000] min [1600000] cur [2268000] turbo mode : enabled Does it do it silently? If so, how can I see the true frequency? -John