Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!oberon!cit-vax!elroy!devvax!rich
From: rich@devvax.JPL.NASA.GOV (Richard Pettit)
Newsgroups: comp.sys.ibm.pc
Subject: Re: 386 rumors, questions, and comments
Message-ID: <367@devvax.JPL.NASA.GOV>
Date: Fri, 11-Sep-87 10:40:50 EDT
Article-I.D.: devvax.367
Posted: Fri Sep 11 10:40:50 1987
Date-Received: Sat, 12-Sep-87 17:32:52 EDT
References: <1014@vi.ri.cmu.edu> <1197@cartan.Berkeley.EDU>
Reply-To: rich@devvax.JPL.NASA.GOV (Richard Pettit)
Organization: Jet Propulsion Laboratory, Pasadena, CA.
Lines: 15
Keywords: protection sun machine

In article <1197@cartan.Berkeley.EDU> ballou@wheatena.UUCP (Kenneth R. Ballou) writes:
>In article <1014@vi.ri.cmu.edu> jfb@vi.ri.cmu.edu (John Brennen) writes:
>...
>Manual to see that in Virtual 8086 mode, the instructions IN, INS, OUT,
>and OUTS are *not* IOPL (I/O Privilege Level) sensitive.  So, for example,
>a user task could reset the CPU in the same way as one resets the 80286 in
>the AT by sending an appropriate command to the 8042.


However, those instructions ARE sensitive to the I/O permission bit map.
Therefore, if you want to allow your virtual PC to reboot the ENTIRE machine,
help yourself. What do you think a V86 monitor is for ? So that you
can model the limitations of the virtual PC.

rich@devvax.jpl.nasa.gov