From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CD5wK-0005l8-Ou for qemu-devel@nongnu.org; Thu, 30 Sep 2004 14:46:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CD5wK-0005ko-4q for qemu-devel@nongnu.org; Thu, 30 Sep 2004 14:46:04 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CD5wK-0005ke-22 for qemu-devel@nongnu.org; Thu, 30 Sep 2004 14:46:04 -0400 Received: from [64.233.170.194] (helo=mproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CD5pG-00008H-R8 for qemu-devel@nongnu.org; Thu, 30 Sep 2004 14:38:47 -0400 Received: by mproxy.gmail.com with SMTP id 73so375365rnl for ; Thu, 30 Sep 2004 11:38:46 -0700 (PDT) Message-ID: <2ad73a04093011386715b824@mail.gmail.com> Date: Thu, 30 Sep 2004 15:38:46 -0300 From: =?ISO-8859-1?Q?Andr=E9_Braga?= Subject: Re: [Qemu-devel] BeOS/Zeta eats 100% cpu time In-Reply-To: <415C41FB.9050701@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable References: <415C0AE6.6000205@gmx.de> <2ad73a04093008366675a85f@mail.gmail.com> <415C2BE2.7070905@gmx.de> <2ad73a040930100714555fe5@mail.gmail.com> <415C41FB.9050701@gmx.de> Reply-To: =?ISO-8859-1?Q?Andr=E9_Braga?= , 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 On Thu, 30 Sep 2004 19:27:23 +0200, Christian Wiese w= rote: > Sorry to be imprecise. The guest (BeOS) is more or less in an idle > state. The host (WinXP) uses 100% cpu time. OK, so before I jump in saying contradictory statements: On VESA/grayscale modes, anything doing rapid video refreshes will tax the CPU. Like playing a video, watching the Chart, moving windows, anything like that. I'm surprised that your BeOS was just sitting idle! > No, I don=B4t think so, because even if I minimize the qEmu window and > nothing changes in BeOS (clock changes only every minute, not second), > the host-CPU is at 100%. This is strange, but now I have another idea: maybe it's requesting the hardware to indeed repaint the screen with a 60 times a second, as by the 60Hz refresh rate to which it defaults when using VESA modes. SDL might not be handling this intelligently, or maybe it's the graphics emulation or the Cirrus BIOS; anyway, QEMU goes idle when I boot a console-mode OS, and goes for 100% CPU when I boot any graphical OS, BeOS included. > I meant: is it possible to activate the old S3 card emulation or was it > never finished? Because when it is possible, I can search for a driver. > If not, I=B4ll try to write a Cirrus driver, but this would take some > time, because I=B4m just looking into some network-driver development. I have no idea. Sorry :) --=20 "Structure is nothing if it is all you've got. Skeletons spook people if they try to walk around on their own; I really wonder why XML does not" Erik Naggum