From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: [patch] vm86: Clear AC on INT
Date: Sun, 28 Jul 2002 20:21:09 +0400 [thread overview]
Message-ID: <3D4419F5.3000104@yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 284 bytes --]
Hello.
According to this:
http://support.intel.com/design/intarch/techinfo/Pentium/instrefi.htm#89126
AC flag is cleared by an INT
instruction executed in real mode.
The attached patch implements that
functionality and solves some
problems recently discussed in
dosemu mailing list.
[-- Attachment #2: vm86_ac.diff --]
[-- Type: text/plain, Size: 550 bytes --]
--- linux/arch/i386/kernel/vm86.c Sat Jul 27 13:12:38 2002
+++ linux/arch/i386/kernel/vm86.c Sat Jul 27 23:56:27 2002
@@ -317,6 +317,11 @@
regs->eflags &= ~TF_MASK;
}
+static inline void clear_AC(struct kernel_vm86_regs * regs)
+{
+ regs->eflags &= ~AC_MASK;
+}
+
/* It is correct to call set_IF(regs) from the set_vflags_*
* functions. However someone forgot to call clear_IF(regs)
* in the opposite case.
@@ -471,6 +476,7 @@
IP(regs) = segoffs & 0xffff;
clear_TF(regs);
clear_IF(regs);
+ clear_AC(regs);
return;
cannot_handle:
next reply other threads:[~2002-07-28 16:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-28 16:21 Stas Sergeev [this message]
2002-08-01 12:19 ` [patch] vm86: Clear AC on INT 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
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=3D4419F5.3000104@yahoo.com \
--to=stssppnn@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--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