Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!cbmvax!daveh
From: daveh@cbmvax.commodore.com (Dave Haynie)
Newsgroups: comp.sys.amiga.tech
Subject: Re: further A2500 speedup?
Message-ID: <14241@cbmvax.commodore.com>
Date: 6 Sep 90 16:37:53 GMT
References: <1990Sep5.171708.8069@athena.mit.edu>
Reply-To: daveh@cbmvax (Dave Haynie)
Organization: Commodore, West Chester, PA
Lines: 23

In article <1990Sep5.171708.8069@athena.mit.edu> rlcarr@athena.mit.edu (Richard L. Carreiro) writes:
>I am running SetCPU1.6 with the FASTROM option.

>Given that, will I get anything out of using the programs (called 
>MOVESSP [or something similar]) which move the system and/or supervisor
>stacks, the main exec structures, and the interrupts into 32-bit RAM?
>Or does SetCPU do that?

SetCPU uses the MMU to relocate the system stack, if it finds the system
stack in Chip memory.  It doesn't try to change VBR (Vector Base Register,
which determines where the vector table used for interrupts and exceptions
is located) or any Exec stuff.  If MOVESSP works without building an MMU
table, it might be useful, and if you run it before SetCPU, you will avoid
moving the system stack twice.  Assuming it works OK in the first place; I
don't anything about MOVESSP except what you've told me.

>Rich Carreiro                                    The "War on Drugs"


-- 
Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
      Get that coffee outta my face, put a Margarita in its place!