Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!UOTTAWA.BITNET!451061
From: 451061@UOTTAWA.BITNET (Valentin Pepelea)
Newsgroups: comp.sys.amiga.tech
Subject: Public Code
Keywords: Code Interrupts Public Hunk Babe Meow!
Message-ID: <8906280338.AA08014@jade.berkeley.edu>
Date: 28 Jun 89 03:24:16 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: Virtual Research
Lines: 23

In the Exec manual, (or was that in the autodocs?) it is said that all
interrupt code and data has to be placed in MEMF_PUBLIC memory, because by
definition, all MEMF_PUBLIC memory also happens to be MEMF_LOCKED memory.
(That was a mistake, there should have been a separate flag for that.)

Well, do the compilers out there indeed tell the linker that the hunks which
contain interrupt code have to be placed in public memory?

For example, lattice has the __interrupt qualifier for functions. What does
that qualifier do? Does it force the linker to load the code in public memory?

This is a signifincant detail, because if indeed all compilers (and
programmers) make sure their interrupt code, and code that calls Forbid() and
Disable() are located in locked memory, then an upcoming virtual memory manager
will have every right to crash programs which do not follow these rules.

Valentin
_________________________________________________________________________
"An  operating  system  without         Name:   Valentin Pepelea
 virtual memory is an operating         Phonet: (613) 231-7476 (New!)
 system without virtue."                Bitnet: 451061@Uottawa.bitnet
                                        Usenet: Use cunyvm.cuny.edu gate
         - Ancient Inca Proverb         Planet: 451061@acadvm1.UOttawa.CA