From: Fabrice Bellard <fabrice@bellard.org>
To: gwa@alumni.cmu.edu, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu and OS/2
Date: Thu, 18 Mar 2004 01:54:15 +0100 [thread overview]
Message-ID: <4058F337.1080703@bellard.org> (raw)
In-Reply-To: <4058EEEA.8000307@grandecom.net>
Greg Alexander wrote:
>
>
> Fabrice Bellard wrote:
>
>> Hi,
>>
>> Can you try the CVS ? I made a specific VGA fix for the OS/2 install
>> (you can see the OS/2 & IBM logo), but there are still problems after.
>>
>> If OS/2 does not rely on segment limit checks or weird FPU exceptions,
>> then there is a chance that QEMU can launch it soon.
>
>
> If I remember correctly, at least the early versions of OS/2 DID rely on
> segment limit checks. This allowed it to do multitaking on 286
> processors, and a lot of that mechanism was still used in the 386 code.
It is possible and easy to add full segment limit and right checks in
QEMU with a runtime selectable option. It would impact mostly 16 bit
code and the slowdown would be small: because QEMU is a dynamic
translator, some tests can be done at translation time.
Unfortunately it is not yet on the top on my TODO list :-(
Fabrice.
prev parent reply other threads:[~2004-03-18 0:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 21:11 [Qemu-devel] qemu and OS/2 Sami Haahtinen
2004-03-15 22:33 ` J. Mayer
2004-03-16 20:03 ` [Qemu-devel] " Sami Haahtinen
2004-03-15 23:59 ` [Qemu-devel] " Fabrice Bellard
2004-03-16 20:03 ` [Qemu-devel] " Sami Haahtinen
2004-03-17 13:17 ` Jocelyn Mayer
2004-03-17 22:02 ` J. Mayer
2004-03-18 21:19 ` Sami Haahtinen
2004-03-18 21:45 ` J. Mayer
2004-03-19 5:31 ` Sami Haahtinen
2004-03-19 6:57 ` J. Mayer
2004-03-19 10:11 ` Sami Haahtinen
2004-03-21 18:34 ` Fabrice Bellard
2004-03-21 21:35 ` Sami Haahtinen
2004-03-18 0:35 ` [Qemu-devel] " Greg Alexander
2004-03-18 0:54 ` 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=4058F337.1080703@bellard.org \
--to=fabrice@bellard.org \
--cc=gwa@alumni.cmu.edu \
--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).