From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JYXel-0006YB-6D for qemu-devel@nongnu.org; Sun, 09 Mar 2008 22:22:27 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JYXej-0006Xn-EA for qemu-devel@nongnu.org; Sun, 09 Mar 2008 22:22:26 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JYXej-0006Xk-A3 for qemu-devel@nongnu.org; Sun, 09 Mar 2008 22:22:25 -0400 Received: from wf-out-1314.google.com ([209.85.200.171]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JYXej-0006Ki-7c for qemu-devel@nongnu.org; Sun, 09 Mar 2008 22:22:25 -0400 Received: by wf-out-1314.google.com with SMTP id 28so1643543wff.4 for ; Sun, 09 Mar 2008 19:22:23 -0700 (PDT) Message-ID: Date: Mon, 10 Mar 2008 09:22:23 +0700 From: "Mulyadi Santosa" Subject: Re: [Qemu-devel] High CPU Usage with Linux 2.6.24 and Windows XP Guest (but not with 2.6.23) In-Reply-To: <46d6db660803091319y508682b5mb8578f2eb716ba3@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080306105838.0ce99a16.lists@pelvoux.nildram.co.uk> <46d6db660803060405nef01989he022ae18a35c6ab5@mail.gmail.com> <20080306143156.5605244c.lists@pelvoux.nildram.co.uk> <46d6db660803070158u7647ea3fg57632cdecb813305@mail.gmail.com> <20080309011414.2f401df6.lists@pelvoux.nildram.co.uk> <46d6db660803091319y508682b5mb8578f2eb716ba3@mail.gmail.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi.. On Mon, Mar 10, 2008 at 3:19 AM, Christian MICHON wrote: > On 3/9/08, Steve Fosdick wrote: > > I have found a single config change that causes the problem. With: > > > > # CONFIG_HIGH_RES_TIMERS is not set > > > > kqemu works correctly, whereas with: > > > > CONFIG_HIGH_RES_TIMERS=y > > > > the problem appears. Any idea why that causes a problem? Is it a bug? More and more I began to suspect it's due to excessive amount of timer rearming plus many below 10ms timer interval. Opinions? regards, Mulyadi.