home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.arch
- Path: sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!eff!ibmpcug!exnet!dhd
- From: dhd@exnet.co.uk (Damon)
- Subject: Re: PALcode instructions vs TRAP instructions
- Message-ID: <Bt4Grs.2Ap@exnet.co.uk>
- Organization: ExNet Systems Ltd Public Access News, London, UK
- References: <1992Aug12.092211.58077@cc.usu.edu> <34303@cbmvax.commodore.com> <1992Aug16.195833.58188@cc.usu.edu>
- Date: Mon, 17 Aug 1992 09:52:39 GMT
- Lines: 26
-
- In article <1992Aug16.195833.58188@cc.usu.edu> ivie@cc.usu.edu (CP/M lives!) writes:
- >In article <34303@cbmvax.commodore.com>, jesup@cbmvax.commodore.com (Randell Jesup) writes:
- >> ivie@cc.usu.edu (CP/M lives!) writes:
- >>>Not really. The OS will believe the console code about how much memory is
- >>>available. The console reports the memory size as smaller than physical by
- >>>the amount of memory needed for the PALcode and the console. The OS will not
- >>>try to use the memory thus reserved for PALcode.
- >>
- >> This would seem to be dangerous, because of wild pointers. Just
- >> because the OS doesn't know about the memory doesn't mean that there won't
- >> be a write to those locations. I do hope that PALcode fetches are checked
- >> for illegal accesses.
- >
- >The problem with wild pointers should be solved as soon as the OS is up far
- >enough to initialize the page tables. If the page tables don't include the
- >console memory, the OS can't get at them.
-
- Mmm. But waht about bugs (eg wild pointers) in the OS? I mean, am I missing
- something, or don't OSes still have bugs in them? B^>/2
-
- Damon
- --
- Damon Hart-Davis | Tel/Fax: +44 81 755 0077 |1.22|| ALL MAIL FREE.
- Internet: dhd@exnet.co.uk | Also: Damon@ed.ac.uk || US hotrod motor groups.
- --------------------------+----------------------++ >12 mail&news polls / day.
- Public access UNIX (Suns), news and mail for #5 per month. FIRST MONTH FREE.
-