qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian Wiese <developlists@gmx.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] BeOS/Zeta eats 100% cpu time
Date: Thu, 30 Sep 2004 19:27:23 +0200	[thread overview]
Message-ID: <415C41FB.9050701@gmx.de> (raw)
In-Reply-To: <2ad73a040930100714555fe5@mail.gmail.com>

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

  reply	other threads:[~2004-09-30 17:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 13:32 [Qemu-devel] BeOS/Zeta eats 100% cpu time Christian Wiese
2004-09-30 15:36 ` André Braga
2004-09-30 15:53   ` Christian Wiese
2004-09-30 17:07     ` André Braga
2004-09-30 17:27       ` Christian Wiese [this message]
2004-09-30 18:38         ` André Braga
2004-09-30 21:22           ` Andreas Bollhalder
2004-10-01  8:14           ` Christian Wiese
2004-10-01 16:24             ` André Braga
2004-10-01 21:06             ` Christian Wiese
2004-10-01 22:24               ` Paul Brook
2004-10-02  3:45                 ` Johannes Schindelin
2004-10-03 18:57                 ` Christian Wiese
2004-10-04  6:41                   ` Johannes Schindelin
2004-10-04  8:09                     ` Christian Wiese

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=415C41FB.9050701@gmx.de \
    --to=developlists@gmx.de \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).