From: Fabrice Bellard <fabrice.bellard@free.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Interpreter for QEMU
Date: Wed, 05 Nov 2003 00:56:14 +0100 [thread overview]
Message-ID: <3FA83C9E.1020001@free.fr> (raw)
In-Reply-To: <Pine.LNX.4.55.0311050211550.10575@home.oyster.ru>
malc wrote:
>>It is true that a solution must be found to accelerate the DOS programs,
>>especially when soft mmu is not in use. [When soft mmu is in use, it is
>>possible to examine exactly each write access to see if the translated
>>code is modified with a byte granularity].
>
>
> I have tried running some demos with softmmu, it provides no noticable
> benefit over hard one.
Write accesses are not verified with a byte granularity yet, but I will
add it soon. It should accelerate the case where code and data are
intermixed.
> If not pagefaults then constant translation block
> generation/recycling will take its toll (but this probably covers mostly
> real-mode or before watcom came into fashion p-mode programs, not that
> i havent seen quite ingenious SMC in DOS4G/W applications)
For self-modifying code, I agree that the translation/recycling stuff is
_very_ slow...
Fabrice.
prev parent reply other threads:[~2003-11-04 23:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 0:58 [Qemu-devel] Interpreter for QEMU malc
2003-11-04 22:46 ` Fabrice Bellard
2003-11-04 23:17 ` malc
2003-11-04 23:56 ` Fabrice Bellard [this message]
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=3FA83C9E.1020001@free.fr \
--to=fabrice.bellard@free.fr \
--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).