From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: AW: Re: Xen 3.4 strange behaviour as compared to Xen 3.3.1 Date: Fri, 29 May 2009 22:30:42 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Carsten Schiers , xen-devel List-Id: xen-devel@lists.xenproject.org Is lowest p-state lowest or highest frequency/voltage? -- Keir On 29/05/2009 17:47, "Carsten Schiers" wrote: > Thanks Keir, I tried it out but there is no difference. And by the way: > it > is in lowest p-state and doesn't come up, even if under heavy load. Hmm. >=20 > BR, > Carsten. >=20 > -----Urspr=FCngliche Nachricht----- > Von: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > Gesendet: Freitag, 29. Mai 2009 17:02 > An: Carsten Schiers; xen-devel > Betreff: Re: [Xen-devel] Xen 3.4 strange behaviour as compared to Xen > 3.3.1 >=20 > On 29/05/2009 15:03, "Carsten Schiers" wrote: >=20 >> - as already reported, ondemand manager in dom0-kernel doesn't step, >> manual >> setting works so it seems a bit like the communication between > dom0 >> and >> hypervisor regarding idle time is not working >=20 > Could be an interaction with C-state support, preferring deep sleep to > running at lower voltage/frequency? You could try no-cpuidle on Xen's > command line at boot time and see if that changes things. >=20 > -- Keir >=20 >> - all beside one domu use Xen 3.4.0 kernel, the one who uses it's >> customized >> kernel won't start up as first domu. It simply hangs and this >> prevents also >> all other domus (I all auto start them, no save/restore) don't > come >> up. When >> I start the chain with a different one and this (with the > different >> kernel) >> is started as #2 or #3, not problem >>=20 >> - one domu is for vdr with three dvb pci cards passed trough. This >> one, when >> started as the first one, will cause xentop to show 20% load. When >> restarted >> or started as #2, the load is like with 3.3.1 at roughly 3-5%. >=20 >=20 >=20 >=20