public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kasper Dupont <kasperd@daimi.au.dk>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	root@chaos.analogic.com, stas.orel@mailcity.com,
	linux-kernel@vger.kernel.org
Subject: Re: [patch] vm86: Clear AC on INT
Date: Thu, 01 Aug 2002 19:04:36 +0200	[thread overview]
Message-ID: <3D496A24.4E134ED5@daimi.au.dk> (raw)
In-Reply-To: Pine.GSO.3.96.1020801183410.8256M-100000@delta.ds2.pg.gda.pl

"Maciej W. Rozycki" wrote:
> 
> On Thu, 1 Aug 2002, Kasper Dupont wrote:
> 
> > Ehrm, that wasn't my point. My point was that if the feature exist
> > in virtual 86 mode but not in real mode, the kernel should prevent
> > it from being used in virtual 86 mode because it is supposed to
> > emulate real mode.
> 
>  The mode is supposed to emulate an 8086 which doesn't have the flag.

OK, but if it is only supposed to emulate an 8086 shouldn't it have
trapped on every instruction not existing on 8086? It doesn't and
that is quite fortunate, because we can then use it for other purposes
namely runing software that expects to have the entire computer for
itself in a multitasking environment. However it seems no matter how
we do it, what is emulated will not work exactly like any CPU in real
mode.

> Any "real mode" code that operates on the AC flag must have been
> created after i386 was released as it requires 32-bit instructions.  Hence
> it has to be prepared to deal with the vm86 mode.

That does make some sense, but not all software written for i386 and
later processors does deal with vm86 in the desired way. Some software
was only intended for real mode when being written, but we might now
want to run it in virtual 86 mode. Thanks to emm386 we probably don't
see many DOS programs not working in virtual 86 mode, but emm386 itself
plain refuses to load in virtual 86 mode.

-- 
Kasper Dupont -- der bruger for meget tid på usenet.
For sending spam use mailto:razrep@daimi.au.dk
or mailto:mcxumhvenwblvtl@skrammel.yaboo.dk

  reply	other threads:[~2002-08-01 17:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-28 16:21 [patch] vm86: Clear AC on INT Stas Sergeev
2002-08-01 12:19 ` Kasper Dupont
2002-08-01 13:43 ` Kasper Dupont
2002-08-01 15:15   ` Richard B. Johnson
2002-08-01 15:49     ` Kasper Dupont
2002-08-01 16:52     ` Alan Cox
2002-08-01 15:55       ` Kasper Dupont
2002-08-01 17:28         ` Alan Cox
2002-08-01 16:21           ` Kasper Dupont
2002-08-01 16:40             ` Maciej W. Rozycki
2002-08-01 17:04               ` Kasper Dupont [this message]
2002-08-01 17:38                 ` Richard B. Johnson
2002-08-01 17:48                   ` Kasper Dupont
2002-08-01 17:47             ` Alan Cox
2002-08-01 16:33   ` Maciej W. Rozycki

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=3D496A24.4E134ED5@daimi.au.dk \
    --to=kasperd@daimi.au.dk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@ds2.pg.gda.pl \
    --cc=root@chaos.analogic.com \
    --cc=stas.orel@mailcity.com \
    /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