From: Kasper Dupont <kasperd@daimi.au.dk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: 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 17:55:27 +0200 [thread overview]
Message-ID: <3D4959EF.15022EE8@daimi.au.dk> (raw)
In-Reply-To: 1028220750.15022.67.camel@irongate.swansea.linux.org.uk
Alan Cox wrote:
>
> On Thu, 2002-08-01 at 16:15, Richard B. Johnson wrote:
> > Alignment-check does not exist in real mode. Therefore AC flags
> > mean nothing. In fact, you can't even access more than 16 bits
> > of the flags register in real mode, even by playing tricks
> > (pushf pushes only 16 bits, even if you prefix it with 0x66).
>
> The kernel using virtual 8086 mode, not real mode. In Virtual 8086 mode
> the alignment trap is enforced and honoured.
Sure, but I guess the kernel is supposed to use virtual 86 mode
to emulate real mode. If it really is true that AC is honoured
in virtual 86 mode but ignored in real mode, then the kernel
should be changed to not enable that flag en virtual 86 mode.
The flag itself should still be simulated using other means.
This would be similar to the use of the use of the VIF flag to
emulate the IF flag. This flag has actually got me wondering:
AFAIR the flag is mentioned in Intel specs, but it looks like
in Linux the flag is implemented 100% in software with no help
from the CPU. Is that correct, or did I miss something?
--
Kasper Dupont -- der bruger for meget tid på usenet.
For sending spam use mailto:razrep@daimi.au.dk
or mailto:mcxumhvenwblvtl@skrammel.yaboo.dk
next prev parent reply other threads:[~2002-08-01 15:52 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 [this message]
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
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=3D4959EF.15022EE8@daimi.au.dk \
--to=kasperd@daimi.au.dk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--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