From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CD4o2-0003x3-3q for qemu-devel@nongnu.org; Thu, 30 Sep 2004 13:33:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CD4o1-0003wr-ML for qemu-devel@nongnu.org; Thu, 30 Sep 2004 13:33:25 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CD4o1-0003wn-II for qemu-devel@nongnu.org; Thu, 30 Sep 2004 13:33:25 -0400 Received: from [213.165.64.20] (helo=mail.gmx.net) by monty-python.gnu.org with smtp (Exim 4.34) id 1CD4h4-00057w-M0 for qemu-devel@nongnu.org; Thu, 30 Sep 2004 13:26:16 -0400 Message-ID: <415C41FB.9050701@gmx.de> Date: Thu, 30 Sep 2004 19:27:23 +0200 From: Christian Wiese MIME-Version: 1.0 Subject: Re: [Qemu-devel] BeOS/Zeta eats 100% cpu time References: <415C0AE6.6000205@gmx.de> <2ad73a04093008366675a85f@mail.gmail.com> <415C2BE2.7070905@gmx.de> <2ad73a040930100714555fe5@mail.gmail.com> In-Reply-To: <2ad73a040930100714555fe5@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit 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 André Braga wrote: >Uh, so you meant having 100% use of CPU on the host machine? > > > Sorry to be imprecise. The guest (BeOS) is more or less in an idle state. The host (WinXP) uses 100% cpu time. >That could be explained by acceleration too. AFAIK, on VESA/monochrome >mode, BeOS has to repaint the entire screen every time something >changes (like the clock on the deskbar). This is not that heavy on the >guest CPU, but on the emulated bus timings and video >bandwidth, which IMO is the biggest bottleneck of QEMU. That could be >the reason, but I may be wrong on my assertment. > > > No, I don´t 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%. >There are drivers for several S3 models available to BeOS, but those >are hardly all the models made by S3. The only two solutions I can >think of is to write a new graphic card emulation layer for QEMU, >which supports the instruction set of a specific, supported card on >BeOS, or to write a new driver for BeOS which drives the Cirrus card >QEMU currently emulates. > > > 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´ll try to write a Cirrus driver, but this would take some time, because I´m just looking into some network-driver development. Greetings, Chris