All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice.bellard@free.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Interpreter for QEMU
Date: Tue, 04 Nov 2003 23:46:47 +0100	[thread overview]
Message-ID: <3FA82C57.1070104@free.fr> (raw)
In-Reply-To: <Pine.LNX.4.55.0311040348270.6264@home.oyster.ru>

It would be interesting to find a way to generate both the dynamic 
translator and the interepreter from the same description. I see that 
you are using ML to generate the interpreter. This is an original choice!

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].

Fabrice.

malc wrote:
> Hello,
> 
> http://www.boblycat.org/~malc/1_iqemu.patch.gz conatains patch against CVS
> version of QEMU that adds interpreted i386 target. Im hoping that someone
> more apt than me can somehow breed it together with dynamic translator, so
> that QEMU will be more viable for DOS emulation (interpreter can help some
> with self-modifying code (so loved by DOS programmers) and/or highly
> interleaved code/data, when host'spage faults take too much time)
> 
> I was able to boot FreeDOS and run some applications with this purely
> interpreted target, though apparently there are still some bugs lurking.
> 
> To apply the patch:
> $ cd cvs/version/of/qemu
> $ zcat patch/location/1_iqemu.patch.gz | patch -p1
> $ ./configure --target-list="i386-softmmu i386-interp"
> $ gmake
> 
> Note that: interpreter is currently x86 specific and there is no FPU
> support whatsoever.
> 
> Sincerely,
> malc
> 

  reply	other threads:[~2003-11-04 22:46 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 [this message]
2003-11-04 23:17   ` malc
2003-11-04 23:56     ` Fabrice Bellard

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=3FA82C57.1070104@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.