Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!noao!arizona!amethyst!spock.ame.arizona.edu!chris
From: chris@spock.ame.arizona.edu (Chris Ott)
Newsgroups: comp.sys.nsc.32k
Subject: Mod Table
Message-ID: <994@amethyst.math.arizona.edu>
Date: 6 Jun 89 18:32:37 GMT
Sender: news@amethyst.math.arizona.edu
Reply-To: chris@spock.ame.arizona.edu (Chris Ott)
Organization: Forensic Productions, Inc.     Tucson, AZ
Lines: 25


agnew@trwrc.UUCP (Robert A. Agnew) writes:
> The National programmer's manual for the 32k says that the module table
> must exist in the first 64k of physical memory. The Texas Instrument
> (second source) programmer's manual for the 32032 states that there can
> be 64k of module table per user.  These statements appear to be
> inconsistent.

     Well, I'm no expert on the 32k (by far), but these don't have to
be inconsistent at all. When the National book says the table must be
in the first 64k of memory, they probably mean the first 64k of _virtual_
memory. Since each user (process?) has his/her own _virtual_ address
space, each user can also have his/her own module table which must be
in the first 64k of that address space.

>               What happens in supervisor mode? Does the super have his
> own module table?  Anyone know the truth on this matter?

     Extrapolating from the above, the supervisor module table probably
has to be in the first 64k of the supervisor address space, whatever
that happens to be.

     (Someone please correct me if I'm wrong.)

Chris