From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: OSS audio debugging
Date: Mon, 14 Jun 2004 21:01:16 +0200 [thread overview]
Message-ID: <40CDF5FC.40707@bellard.org> (raw)
In-Reply-To: <000d01c451e5$36a1a3a0$0401a8c0@putte2k>
Mike Nordell wrote:
> DOOM Shareware - this one needs no introduction.
> Crashes, hangs and plays really "choppy" sound.
> The crashes and hangs (depending on moon-phase) seems to be due to
> incomplete detection of self-modifying code. When it does run for more than
> 1 second, the choppy sound I suspect might be, as for many cases here, due
> to timing or incorrect SB16, PIC or DMA emulation. That it also run as in
> molasses (the seconds I got it to run) further strengthen my suspicions of
> timing or PIC - even that it could be a large amount of self-modifying code
> invalidating the TB all the time too. I haven't dug deeper into it.
It should work now. The problem was linked to self modifying code and
cpu interrupts.
DOOM is a rather pathological case for self-modifying code and it slows
QEMU a lot (although DOOM remains fully playable on my PC). Since only
some instruction constants are modified in the code, I could optimize
this case specifically in the dynamic compiler.
Fabrice.
next prev parent reply other threads:[~2004-06-14 18:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 7:57 [Qemu-devel] Re: OSS audio debugging Mike Nordell
2004-06-14 9:02 ` malc
2004-06-14 15:56 ` malc
2004-06-14 19:01 ` Fabrice Bellard [this message]
2004-06-14 19:24 ` [Qemu-devel] compile error (current CVS) Grzegorz Kulewski
2004-06-15 11:39 ` vaise
2004-06-15 14:09 ` [OK NOW] " Grzegorz Kulewski
2004-06-15 21:59 ` [Qemu-devel] Re: [OK NOW] " Gabriel Ebner
2004-06-14 19:29 ` [Qemu-devel] Re: OSS audio debugging Jean-Michel POURE
-- strict thread matches above, loose matches on Subject: below --
2004-06-10 22:59 Mike Nordell
2004-06-11 5:23 ` malc
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=40CDF5FC.40707@bellard.org \
--to=fabrice@bellard.org \
--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).