Mail Archives: djgpp/1999/04/29/07:50:46
From: | Alberto Chessa <achessa AT fiar DOT finmeccanica DOT it>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | DPMI: disabling interrupt ap privilage level 0
|
Date: | Thu, 29 Apr 1999 12:17:10 +0200
|
Organization: | TIN
|
Lines: | 13
|
Message-ID: | <372831A6.CD547540@fiar.finmeccanica.it>
|
NNTP-Posting-Host: | a-mi21-39.tin.it
|
Mime-Version: | 1.0
|
X-Mailer: | Mozilla 4.5 [en] (Win95; I)
|
X-Accept-Language: | en
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Reply-To: | djgpp AT delorie DOT com
|
It is possible, running under CWSDPR0, to directly manage CPU interrupt
flag via CLI and STI (and IRET, POPF) ?
Are these instruction slow, that is are they trapped by the VM monitor ?
The DJGPP function disable()/enable(), implemented via
dpmi_get_and_disable/enable_interrut(), reflect virtual interrupt state
on the CPU interrupt flag ?
This is an OT question but actually I do not know a better NG for it.
Thanks in advance.
- Raw text -