Article View: comp.arch
Article #11299Re: DEC Alpha architecture issues
From: Michael Woodacre
Date: Thu, 19 Nov 1992 16:14
Date: Thu, 19 Nov 1992 16:14
50 lines
2973 bytes
2973 bytes
In article <1992Nov18.210416.27212@nntpd.lkg.dec.com>,
dipirro@star.dec.com (Steve DiPirro) writes:
>
> In article <1992Nov18.112407.2518@doug.cae.wisc.edu>,
keiths@cae.wisc.edu (Keith Scidmore) writes...
> >2. The Alpha architecture also includes a feature they call PALcode that
> > allows the chip to have a sort of rom-bios. Why is it useful to have
> > this feature? Supposedly Operating systems can make use of this for
> > the implementation of certain system calls.
>
> PALcode allows for the implementation of uniprocessor-atomic
> "instructions" which are actually a sequence of Alpha instructions.
> It allows the architecture to remain pure RISC and not compromise
> performance to implement some complex instructions. This was very
> useful in the port of VMS to Alpha.
Can you explain how this is different from kernel code with interrupts
disabled on any other risc processor? For instance, an R4000 can
implement uniprocessor-atomic "instructions" which are sequences of
MIPS instructions to implement complex functions by running code
in kernel level with interrupts switched off.
>
> Take the VAX REI instruction as an example. This is a very complex
> VAX instruction and is implemented in PALcode on Alpha (for VMS).
> So there is no need to burden the base architecture with the
> implementation of an REI instruction. Instead, you have a "subroutine"
> of sorts which executes in the special PALcode environment.
>
> Very few PALcode instructions were actually needed to port VMS to
> Alpha, but some we could not do without (without considerable work,
> that is).
>
> PALcode is also a convenient place to handle device interrupts and
> exceptions and provide the expected OS interfaces at that level.
> Specific OS knowledge can also be built into PALcode, such as pagetable
> formats, etc. allowing such things as TB invalidates to be handled
> by PALcode. For VMS, PALcode also handles unaligned data reference
> fixups, providing an optional exception through the SCB when one occurs.
>
> ------------
> Steve DiPirro dipirro@star.dec.com
> --or-- ...!decwrl!star.dec.com!dipirro
> --or-- dipirro%star.dec@decwrl.dec.com
> ------------
Michael S. Woodacre | Phone: (415) 390 4175
UUCP: {ames,pyramid,decwrl}!mips!woodacre OR woodacre@sgi.com
USPS: MIPS Technologies Inc, M/S 10U-178,
2011 N. Shoreline Blvd, Mountain View, CA 94039
Technical Details
Message-ID:
<lgnfc3INNqnt@spim.mti.sgi.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!think.com!ames!sgi!mips!mips.com!woodacreReferences:
<1992Nov18.210416.27212@nntpd.lkg.dec.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!think.com!ames!sgi!mips!mips.com!woodacre From: woodacre@mips.com (Michael Woodacre) Newsgroups: comp.arch Subject: Re: DEC Alpha architecture issues Followup-To: comp.arch Date: 19 Nov 1992 16:14:59 GMT Organization: Mips Technologies, Inc. Lines: 53 Distribution: world Message-ID: <lgnfc3INNqnt@spim.mti.sgi.com> References: <1992Nov18.210416.27212@nntpd.lkg.dec.com> Reply-To: woodacre@mips.com (Michael Woodacre) NNTP-Posting-Host: krell.mti.sgi.com