From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CD4VY-00088e-1b for qemu-devel@nongnu.org; Thu, 30 Sep 2004 13:14:20 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CD4VX-00087a-3H for qemu-devel@nongnu.org; Thu, 30 Sep 2004 13:14:19 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CD4VW-00087X-Vp for qemu-devel@nongnu.org; Thu, 30 Sep 2004 13:14:19 -0400 Received: from [64.233.170.200] (helo=mproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CD4P5-0001uL-Ol for qemu-devel@nongnu.org; Thu, 30 Sep 2004 13:07:39 -0400 Received: by mproxy.gmail.com with SMTP id 73so3107512rnk for ; Thu, 30 Sep 2004 10:07:39 -0700 (PDT) Message-ID: <2ad73a040930100714555fe5@mail.gmail.com> Date: Thu, 30 Sep 2004 14:07:38 -0300 From: =?ISO-8859-1?Q?Andr=E9_Braga?= Subject: Re: [Qemu-devel] BeOS/Zeta eats 100% cpu time In-Reply-To: <415C2BE2.7070905@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> 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 Uh, so you meant having 100% use of CPU on the host machine? 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. 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. --=20 "Wherever you go, There you are" Buckaroo Banzai On Thu, 30 Sep 2004 17:53:06 +0200, Christian Wiese w= rote: > Hmm. That could be a reason. But a strange thing is, that BeOS itself > thought that it is using only little amount of cpu-time. And for example > vmWare has no problem with this. So, could there be a second problem? > Btw. I=B4ve found in the sources that now there is a Cirrus GraKa > emulated. But before there were a S3 (?). Was the S3 running? Or is it > possible to use the S3 emulation? I think there was a S3 driver for BeOS.= .. >=20 > Thanks so far, >=20 >=20 > Chris