From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [kvm-devel] kvm somehow exempt from frequency scaling? Date: Sun, 06 Jul 2008 15:13:41 +0300 Message-ID: <4870B6F5.9000004@qumranet.com> References: <87veg6bck6.fsf@grogan.peloton> <4619EB19.20305@qumranet.com> <87mz1gj1pr.fsf@grogan.peloton> <461B3CBB.3040401@qumranet.com> <461B63E4.3080804@mr511.de> <87hcrnciom.fsf@grogan.peloton> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: David Abrahams Return-path: In-Reply-To: <87hcrnciom.fsf@grogan.peloton> Sender: kvm-owner@vger.kernel.org List-ID: [Resurrecting old thread] David Abrahams wrote: > on Tue Apr 10 2007, Michael Riepe wrote: > > >> Hi! >> >> Avi Kivity wrote: >> >> >>> Sounds like ondemand is broken. >>> >> Maybe it only switches when the load rises in user space. With KVM, it >> appears in system space. Got to cross-check that on my Core Duo. >> > > More data: it definitely seems to make a difference whether the VM's > desktop is showing. If I switch Gnome workspaces so it's not visible, > it doesn't seem to drive the frequency up. > > This just happened to me. I noticed that if I switch the workspace using alt-ctrl-left while the qemu window is active, qemu hangs. On the other hand, if I switch using the mouse, or while some other window is active, everything is fine. The qemu code even explains this as an sdl bug. Jingle any bells? -- error compiling committee.c: too many arguments to function