Re: [Qemu-devel] BeOS/Zeta eats 100% cpu time

["André Braga" <meianoite@gmail.com>]

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.


-- 
"Wherever you go, There you are"
Buckaroo Banzai



On Thu, 30 Sep 2004 17:53:06 +0200, Christian Wiese <developlists@gmx.de> wrote:
> 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´ve 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...
> 
> Thanks so far,
> 
> 
>  Chris