From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FICgw-0001Zm-0U for qemu-devel@nongnu.org; Sat, 11 Mar 2006 17:36:06 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FICgt-0001Za-UZ for qemu-devel@nongnu.org; Sat, 11 Mar 2006 17:36:05 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FICgt-0001ZX-LP for qemu-devel@nongnu.org; Sat, 11 Mar 2006 17:36:03 -0500 Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1FICkV-0006Ys-AS for qemu-devel@nongnu.org; Sat, 11 Mar 2006 17:39:47 -0500 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FICgo-0001Bo-JF for qemu-devel@nongnu.org; Sat, 11 Mar 2006 23:35:58 +0100 Received: from dslb-084-061-128-228.pools.arcor-ip.net ([84.61.128.228]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 11 Mar 2006 23:35:58 +0100 Received: from skoehler by dslb-084-061-128-228.pools.arcor-ip.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 11 Mar 2006 23:35:58 +0100 From: =?ISO-8859-15?Q?Sven_K=F6hler?= Date: Sat, 11 Mar 2006 23:35:48 +0100 Message-ID: References: <200603112225.16535.paul@codesourcery.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit In-Reply-To: <200603112225.16535.paul@codesourcery.com> Sender: news Subject: [Qemu-devel] Re: qemu (cvs-version) performance? 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 >> I thought, that qemu-0.8.0's problem would be disk-IO. I installed >> Windows 2000 and in the task-manager the CPU-Time is 100% during intense >> IO. A "dir c:\ /A /S /B >NUL:" on the console causes 100% CPU-time and >> most of it being that red-colored "in-kernel-time". > > Qemu host IO is syncrhonous. ie. the guest is paused on the instruction that > issues the IO until the IO completes. As for as the guest is concerned it > happens instantly. This is all your test shows. I have seen thoughts about asynchronous IO for qemu. I thought that they would have been integrated along with the DMA-patches already. I would really see how qemu performs with asynch IO enabled. Are there any patches out there? Greetings Sven